Voice identification in digital assistant systems

ABSTRACT

Systems and processes for operating an intelligent automated assistant are provided. An example method includes receiving, from one or more external electronic devices, a plurality of speaker profiles for a plurality of users; receiving a natural language speech input; determining, based on comparing the natural language speech input to the plurality of speaker profiles: a first likelihood that the natural language speech input corresponds to a first user of the plurality of users; and a second likelihood that the natural language speech input corresponds to a second user of the plurality of users; determining whether the first likelihood and the second likelihood are within a first threshold; and in accordance with determining that the first likelihood and the second likelihood are not within the first threshold: providing a response to the natural language speech input, the response being personalized for the first user.

This application is a continuation of U.S. patent application Ser. No.16/815,984, entitled “VOICE IDENTIFICATION IN DIGITAL ASSISTANTSYSTEMS,” filed on Mar. 11, 2020, which claims priority to U.S.Provisional Patent Application No. 62/855,778, entitled “VOICEIDENTIFICATION IN DIGITAL ASSISTANT SYSTEMS,” filed on May 31, 2019. Thecontents of each of these applications are hereby incorporated byreference in their entireties.

FIELD

This relates generally to intelligent automated assistants and, morespecifically, to identifying users of intelligent automated assistantsin a multi-user or shared environment.

BACKGROUND

Intelligent automated assistants (or digital assistants) can provide abeneficial interface between human users and electronic devices. Suchassistants can allow users to interact with devices or systems usingnatural language in spoken and/or text forms. For example, a user canprovide a speech input containing a user request to a digital assistantoperating on an electronic device. The digital assistant can interpretthe user's intent from the speech input and operationalize the user'sintent into tasks. The tasks can then be performed by executing one ormore services of the electronic device, and a relevant output responsiveto the user request can be returned to the user.

A digital assistant can operate on a device shared by many users.Accordingly, it can be desirable for the digital assistant to identify acurrent user of the device in a multi-user or shared environment.

SUMMARY

Example methods are disclosed herein. An example method includes, at anelectronic device having one or more processors and memory: receiving,from one or more external electronic devices, a plurality of speakerprofiles for a plurality of users; receiving a natural language speechinput; determining, based on comparing the natural language speech inputto the plurality of speaker profiles: a first likelihood that thenatural language speech input corresponds to a first user of theplurality of users; and a second likelihood that the natural languagespeech input corresponds to a second user of the plurality of users, thesecond likelihood being less than the first likelihood; determiningwhether the first likelihood and the second likelihood are within afirst threshold; and in accordance with determining that the firstlikelihood and the second likelihood are not within the first threshold:providing a response to the natural language speech input, the responsebeing personalized for the first user.

Example non-transitory computer-readable media are disclosed herein. Anexample non-transitory computer-readable storage medium stores one ormore programs. The one or more programs comprise instructions, whichwhen executed by one or more processors of an electronic device, causethe electronic device to: receive, from one or more external electronicdevices, a plurality of speaker profiles for a plurality of users;receive a natural language speech input; determine, based on comparingthe natural language speech input to the plurality of speaker profiles:a first likelihood that the natural language speech input corresponds toa first user of the plurality of users; and a second likelihood that thenatural language speech input corresponds to a second user of theplurality of users, the second likelihood being less than the firstlikelihood; determine whether the first likelihood and the secondlikelihood are within a first threshold; and in accordance withdetermining that the first likelihood and the second likelihood are notwithin the first threshold: provide a response to the natural languagespeech input, the response being personalized for the first user.

Example electronic devices are disclosed herein. An example electronicdevice comprises one or more processors; a memory; and one or moreprograms, where the one or more programs are stored in the memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving, from one or moreexternal electronic devices, a plurality of speaker profiles for aplurality of users; receiving a natural language speech input;determining, based on comparing the natural language speech input to theplurality of speaker profiles: a first likelihood that the naturallanguage speech input corresponds to a first user of the plurality ofusers; and a second likelihood that the natural language speech inputcorresponds to a second user of the plurality of users, the secondlikelihood being less than the first likelihood; determining whether thefirst likelihood and the second likelihood are within a first threshold;and in accordance with determining that the first likelihood and thesecond likelihood are not within the first threshold: providing aresponse to the natural language speech input, the response beingpersonalized for the first user.

An example electronic device comprises means for: receiving, from one ormore external electronic devices, a plurality of speaker profiles for aplurality of users; receiving a natural language speech input;determining, based on comparing the natural language speech input to theplurality of speaker profiles: a first likelihood that the naturallanguage speech input corresponds to a first user of the plurality ofusers; and a second likelihood that the natural language speech inputcorresponds to a second user of the plurality of users, the secondlikelihood being less than the first likelihood; determining whether thefirst likelihood and the second likelihood are within a first threshold;and in accordance with determining that the first likelihood and thesecond likelihood are not within the first threshold: providing aresponse to the natural language speech input, the response beingpersonalized for the first user.

Example methods are disclosed herein. An example method includes, at anelectronic device having one or more processors and memory: receiving aspoken media request; determining whether a user, of a plurality ofregistered users, corresponds to the spoken media request; in accordancewith determining that a first user of the plurality of registered userscorresponds to the spoken media request: providing a first response tothe spoken media request, the first response being personalized for thefirst user; and in accordance with determining that no user of theplurality of registered users corresponds to the spoken media request:determining whether the spoken media request includes a personal mediarequest; in accordance with determining that the spoken media requestincludes a personal media request: obtaining an identification of a userwho provided the spoken media request; and in accordance with obtainingthe identification: providing a second response to the spoken mediarequest, the second response being personalized for the user whoprovided the spoken media request.

Example non-transitory computer-readable media are disclosed herein. Anexample non-transitory computer-readable storage medium stores one ormore programs. The one or more programs comprise instructions, whichwhen executed by one or more processors of an electronic device, causethe electronic device to: receive a spoken media request; determinewhether a user, of a plurality of registered users, corresponds to thespoken media request; in accordance with determining that a first userof the plurality of registered users corresponds to the spoken mediarequest: provide a first response to the spoken media request, the firstresponse being personalized for the first user; and in accordance withdetermining that no user of the plurality of registered userscorresponds to the spoken media request: determine whether the spokenmedia request includes a personal media request; in accordance withdetermining that the spoken media request includes a personal mediarequest: obtain an identification of a user who provided the spokenmedia request; and in accordance with obtaining the identification:provide a second response to the spoken media request, the secondresponse being personalized for the user who provided the spoken mediarequest.

Example electronic devices are disclosed herein. An example electronicdevice comprises one or more processors; a memory; and one or moreprograms, where the one or more programs are stored in the memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: receiving a spoken media request;determining whether a user, of a plurality of registered users,corresponds to the spoken media request; in accordance with determiningthat a first user of the plurality of registered users corresponds tothe spoken media request: providing a first response to the spoken mediarequest, the first response being personalized for the first user; andin accordance with determining that no user of the plurality ofregistered users corresponds to the spoken media request: determiningwhether the spoken media request includes a personal media request; inaccordance with determining that the spoken media request includes apersonal media request: obtaining an identification of a user whoprovided the spoken media request; and in accordance with obtaining theidentification: providing a second response to the spoken media request,the second response being personalized for the user who provided thespoken media request.

An example electronic device comprises means for: receiving a spokenmedia request; determining whether a user, of a plurality of registeredusers, corresponds to the spoken media request; in accordance withdetermining that a first user of the plurality of registered userscorresponds to the spoken media request: providing a first response tothe spoken media request, the first response being personalized for thefirst user and in accordance with determining that no user of theplurality of registered users corresponds to the spoken media request:determining whether the spoken media request includes a personal mediarequest; in accordance with determining that the spoken media requestincludes a personal media request: obtaining an identification of a userwho provided the spoken media request; and in accordance with obtainingthe identification: providing a second response to the spoken mediarequest, the second response being personalized for the user whoprovided the spoken media request.

Determining, based on comparing the natural language speech input to theplurality of speaker profiles: a first likelihood that the naturallanguage speech input corresponds to a first user of the plurality ofusers; and a second likelihood that the natural language speech inputcorresponds to a second user of the plurality of users, the secondlikelihood being less than the first likelihood allows a digitalassistant to identify a current user. For example, if the digitalassistant operates on a device shared by many users, the digitalassistant can identify a current user of the device (e.g., based on hisor her speech input) and provide a response (and/or perform a task)personalized for the identified user (e.g., reading the user's textmessages, adding an event to the user's calendar, calling one of theuser's contacts, and the like). Thus, electronic devices shared by manyusers may accurately identify a current user and provide personalcontent for the identified user. In this manner, the user deviceinterface may be made more efficient (e.g., by efficiently providingresponses relevant to an identified user, by increasing the amount ofinformation shared electronic devices can provide, by preventingdisclosure of personal information to unidentified users), whichadditionally reduces power usage and improves battery life of the deviceby enabling the user to use the device more quickly and efficiently.

In accordance with determining that the first likelihood and the secondlikelihood are not within the first threshold: providing a response tothe natural language speech input, the response being personalized forthe first user allows a digital assistant to determine whether a currentuser can be distinguished from other users before providing a responsepersonalized for the current user. This may enhance the security of theuser's personal information by preventing other users from accessingsuch information. Additionally, determining whether a current user canbe distinguished from other users of an electronic device improves theaccuracy of user identification (e.g., especially when the electronicdevice is shared by many users). As discussed, accurately identifying acurrent user and providing personal content for the identified usermakes the user device interface more efficient (e.g., by efficientlyproviding responses relevant to an identified user, by increasing theamount of information shared electronic devices can provide, bypreventing disclosure of personal information to unidentified users),which additionally reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In accordance with determining that a first user of the plurality ofregistered users corresponds to the spoken media request: providing afirst response to the spoken media request, the first response beingpersonalized for the first user allows electronic devices shared by manyusers to provide or modify media content for an identified user. Thus,responses to spoken media requests may be advantageously personalizedfor the identified user (e.g., playing music from the identified user'saccount, adding media content to the identified user's account,providing the news from the identified user's preferred contentprovider, and the like). Further, unauthorized modification or provisionof users' media content may be prevented (e.g., by preventing one userof a shared device from modifying the media content of another user ofthe device). In this manner, the user device interface may be made moreefficient (e.g., by providing media content relevant to an identifieduser, by preventing other users from modifying a user's media content,by allowing a shared device to efficiently and securely manage the mediacontent of multiple users), which additionally reduces power usage andimproves battery life of the device by enabling the user to use thedevice more quickly and efficiently.

In accordance with determining that the spoken media request includes apersonal media request: obtaining an identification of a user whoprovided the spoken media request; and in accordance with obtaining theidentification: providing a second response to the spoken media request,the second response being personalized for the user who provided thespoken media request allows electronic devices shared by many users tosecurely provide or modify media content for an identified user. Forexample, if the device is insufficiently confident that a spoken requestcorresponds to a user, the device can use other techniques (e.g., otherthan using the spoken request) to identify the user before providing apersonalized response. This can increase the security of the user'smedia content by preventing other users from accessing and/or modifyingthe user's media content. Further, obtaining an identification of a userwho provided the spoken media request in accordance with determiningthat the spoken media request includes a personal media request mayallow other techniques to identify a user to be performed only whenappropriate (e.g., when the spoken media request includes a personalrequest). For example, a device may not undesirably perform othertechniques to identify a user (e.g., initiate a dialogue with the user)for spoken media requests not requiring user identification (e.g., “playmusic”). As another example, a device may perform other techniques toidentify a user when user identification is desirable (e.g., forrequests such as “add this to my playlist,” “play my personal music”).Thus, devices may efficiently and securely provide or modify mediacontent without prolonging user device interaction. In this manner, theuser device interface may be made more efficient (e.g., by providingmedia content relevant to an identified user, by preventing other usersfrom modifying a user's media content, by allowing a shared device toefficiently and securely manage the media content of multiple users),which additionally reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a system and environment forimplementing a digital assistant, according to various examples.

FIG. 2A is a block diagram illustrating a portable multifunction deviceimplementing the client-side portion of a digital assistant, accordingto various examples.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling, according to various examples.

FIG. 3 illustrates a portable multifunction device implementing theclient-side portion of a digital assistant, according to variousexamples.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface, according to various examples.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device, according to variousexamples.

FIG. 5B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the display,according to various examples.

FIG. 6A illustrates a personal electronic device, according to variousexamples.

FIG. 6B is a block diagram illustrating a personal electronic device,according to various examples.

FIG. 7A is a block diagram illustrating a digital assistant system or aserver portion thereof, according to various examples.

FIG. 7B illustrates the functions of the digital assistant shown in FIG.7A, according to various examples.

FIG. 7C illustrates a portion of an ontology, according to variousexamples.

FIG. 8 illustrates a user interaction with an electronic device,according to some examples.

FIGS. 9A-F illustrate a flowchart of a process for responding to speechinput, according to some examples.

FIGS. 10A-H illustrate exemplary user interactions with an electronicdevice.

FIGS. 11A-B illustrate a flowchart of a process for providing mediacontent, according to some examples.

FIG. 12 illustrates an exemplary system for obtaining personalinformation.

FIGS. 13A-G illustrate a process for responding to speech input,according to some examples.

FIGS. 14A-E illustrate a process for providing media content, accordingto some examples.

DETAILED DESCRIPTION

In the following description of examples, reference is made to theaccompanying drawings in which are shown by way of illustration specificexamples that can be practiced. It is to be understood that otherexamples can be used and structural changes can be made withoutdeparting from the scope of the various examples.

This generally relates to identifying users of digital assistants basedon their respective voices. Once a user is identified, a digitalassistant can provide a response personalized for the user.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first input could be termed a second input, and,similarly, a second input could be termed a first input, withoutdeparting from the scope of the various described examples. The firstinput and the second input are both inputs and, in some cases, areseparate and different inputs.

The terminology used in the description of the various describedexamples herein is for the purpose of describing particular examplesonly and is not intended to be limiting. As used in the description ofthe various described examples and the appended claims, the singularforms “a,” “an,” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will also beunderstood that the term “and/or” as used herein refers to andencompasses any and all possible combinations of one or more of theassociated listed items. It will be further understood that the terms“includes,” “including,” “comprises,” and/or “comprising,” when used inthis specification, specify the presence of stated features, integers,steps, operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

1. System and Environment

FIG. 1 illustrates a block diagram of system 100 according to variousexamples. In some examples, system 100 implements a digital assistant.The terms “digital assistant,” “virtual assistant,” “intelligentautomated assistant,” or “automatic digital assistant” refer to anyinformation processing system that interprets natural language input inspoken and/or textual form to infer user intent, and performs actionsbased on the inferred user intent. For example, to act on an inferreduser intent, the system performs one or more of the following:identifying a task flow with steps and parameters designed to accomplishthe inferred user intent, inputting specific requirements from theinferred user intent into the task flow; executing the task flow byinvoking programs, methods, services, APIs, or the like; and generatingoutput responses to the user in an audible (e.g., speech) and/or visualform.

Specifically, a digital assistant is capable of accepting a user requestat least partially in the form of a natural language command, request,statement, narrative, and/or inquiry. Typically, the user request seekseither an informational answer or performance of a task by the digitalassistant. A satisfactory response to the user request includes aprovision of the requested informational answer, a performance of therequested task, or a combination of the two. For example, a user asksthe digital assistant a question, such as “Where am I right now?” Basedon the user's current location, the digital assistant answers, “You arein Central Park near the west gate.” The user also requests theperformance of a task, for example, “Please invite my friends to mygirlfriend's birthday party next week.” In response, the digitalassistant can acknowledge the request by saying “Yes, right away,” andthen send a suitable calendar invite on behalf of the user to each ofthe user's friends listed in the user's electronic address book. Duringperformance of a requested task, the digital assistant sometimesinteracts with the user in a continuous dialogue involving multipleexchanges of information over an extended period of time. There arenumerous other ways of interacting with a digital assistant to requestinformation or performance of various tasks. In addition to providingverbal responses and taking programmed actions, the digital assistantalso provides responses in other visual or audio forms, e.g., as text,alerts, music, videos, animations, etc.

As shown in FIG. 1, in some examples, a digital assistant is implementedaccording to a client-server model. The digital assistant includesclient-side portion 102 (hereafter “DA client 102”) executed on userdevice 104 and server-side portion 106 (hereafter “DA server 106”)executed on server system 108. DA client 102 communicates with DA server106 through one or more networks 110. DA client 102 provides client-sidefunctionalities such as user-facing input and output processing andcommunication with DA server 106. DA server 106 provides server-sidefunctionalities for any number of DA clients 102 each residing on arespective user device 104.

In some examples, DA server 106 includes client-facing I/O interface112, one or more processing modules 114, data and models 116, and I/Ointerface to external services 118. The client-facing I/O interface 112facilitates the client-facing input and output processing for DA server106. One or more processing modules 114 utilize data and models 116 toprocess speech input and determine the user's intent based on naturallanguage input. Further, one or more processing modules 114 perform taskexecution based on inferred user intent. In some examples, DA server 106communicates with external services 120 through network(s) 110 for taskcompletion or information acquisition. I/O interface to externalservices 118 facilitates such communications.

User device 104 can be any suitable electronic device. In some examples,user device 104 is a portable multifunctional device (e.g., device 200,described below with reference to FIG. 2A), a multifunctional device(e.g., device 400, described below with reference to FIG. 4), or apersonal electronic device (e.g., device 600, described below withreference to FIG. 6A-B.) A portable multifunctional device is, forexample, a mobile telephone that also contains other functions, such asPDA and/or music player functions. Specific examples of portablemultifunction devices include the Apple Watch, iPhone®, iPod Touch®, andiPad® devices from Apple Inc. of Cupertino, Calif. Other examples ofportable multifunction devices include, without limitation,earphones/headphones, speakers, and laptop or tablet computers. Further,in some examples, user device 104 is a non-portable multifunctionaldevice. In particular, user device 104 is a desktop computer, a gameconsole, a speaker, a television, or a television set-top box. In someexamples, user device 104 includes a touch-sensitive surface (e.g.,touch screen displays and/or touchpads). Further, user device 104optionally includes one or more other physical user-interface devices,such as a physical keyboard, a mouse, and/or a joystick. Variousexamples of electronic devices, such as multifunctional devices, aredescribed below in greater detail.

Examples of communication network(s) 110 include local area networks(LAN) and wide area networks (WAN), e.g., the Internet. Communicationnetwork(s) 110 is implemented using any known network protocol,including various wired or wireless protocols, such as, for example,Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), codedivision multiple access (CDMA), time division multiple access (TDMA),Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or anyother suitable communication protocol.

Server system 108 is implemented on one or more standalone dataprocessing apparatus or a distributed network of computers. In someexamples, server system 108 also employs various virtual devices and/orservices of third-party service providers (e.g., third-party cloudservice providers) to provide the underlying computing resources and/orinfrastructure resources of server system 108.

In some examples, user device 104 communicates with DA server 106 viasecond user device 122. Second user device 122 is similar or identicalto user device 104. For example, second user device 122 is similar todevices 200, 400, or 600 described below with reference to FIGS. 2A, 4,and 6A-B. User device 104 is configured to communicatively couple tosecond user device 122 via a direct communication connection, such asBluetooth, NFC, BTLE, or the like, or via a wired or wireless network,such as a local Wi-Fi network. In some examples, second user device 122is configured to act as a proxy between user device 104 and DA server106. For example, DA client 102 of user device 104 is configured totransmit information (e.g., a user request received at user device 104)to DA server 106 via second user device 122. DA server 106 processes theinformation and returns relevant data (e.g., data content responsive tothe user request) to user device 104 via second user device 122.

In some examples, user device 104 is configured to communicateabbreviated requests for data to second user device 122 to reduce theamount of information transmitted from user device 104. Second userdevice 122 is configured to determine supplemental information to add tothe abbreviated request to generate a complete request to transmit to DAserver 106. This system architecture can advantageously allow userdevice 104 having limited communication capabilities and/or limitedbattery power (e.g., a watch or a similar compact electronic device) toaccess services provided by DA server 106 by using second user device122, having greater communication capabilities and/or battery power(e.g., a mobile phone, laptop computer, tablet computer, or the like),as a proxy to DA server 106. While only two user devices 104 and 122 areshown in FIG. 1, it should be appreciated that system 100, in someexamples, includes any number and type of user devices configured inthis proxy configuration to communicate with DA server system 106.

Although the digital assistant shown in FIG. 1 includes both aclient-side portion (e.g., DA client 102) and a server-side portion(e.g., DA server 106), in some examples, the functions of a digitalassistant are implemented as a standalone application installed on auser device. In addition, the divisions of functionalities between theclient and server portions of the digital assistant can vary indifferent implementations. For instance, in some examples, the DA clientis a thin-client that provides only user-facing input and outputprocessing functions, and delegates all other functionalities of thedigital assistant to a backend server.

2. Electronic Devices

Attention is now directed toward embodiments of electronic devices forimplementing the client-side portion of a digital assistant. FIG. 2A isa block diagram illustrating portable multifunction device 200 withtouch-sensitive display system 212 in accordance with some embodiments.Touch-sensitive display 212 is sometimes called a “touch screen” forconvenience and is sometimes known as or called a “touch-sensitivedisplay system.” Device 200 includes memory 202 (which optionallyincludes one or more computer-readable storage mediums), memorycontroller 222, one or more processing units (CPUs) 220, peripheralsinterface 218, RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, input/output (I/O) subsystem 206, other input controldevices 216, and external port 224. Device 200 optionally includes oneor more optical sensors 264. Device 200 optionally includes one or morecontact intensity sensors 265 for detecting intensity of contacts ondevice 200 (e.g., a touch-sensitive surface such as touch-sensitivedisplay system 212 of device 200). Device 200 optionally includes one ormore tactile output generators 267 for generating tactile outputs ondevice 200 (e.g., generating tactile outputs on a touch-sensitivesurface such as touch-sensitive display system 212 of device 200 ortouchpad 455 of device 400). These components optionally communicateover one or more communication buses or signal lines 203.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 200 is only one example of aportable multifunction device, and that device 200 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 2A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 202 includes one or more computer-readable storage mediums. Thecomputer-readable storage mediums are, for example, tangible andnon-transitory. Memory 202 includes high-speed random access memory andalso includes non-volatile memory, such as one or more magnetic diskstorage devices, flash memory devices, or other non-volatile solid-statememory devices. Memory controller 222 controls access to memory 202 byother components of device 200.

In some examples, a non-transitory computer-readable storage medium ofmemory 202 is used to store instructions (e.g., for performing aspectsof processes described below) for use by or in connection with aninstruction execution system, apparatus, or device, such as acomputer-based system, processor-containing system, or other system thatcan fetch the instructions from the instruction execution system,apparatus, or device and execute the instructions. In other examples,the instructions (e.g., for performing aspects of the processesdescribed below) are stored on a non-transitory computer-readablestorage medium (not shown) of the server system 108 or are dividedbetween the non-transitory computer-readable storage medium of memory202 and the non-transitory computer-readable storage medium of serversystem 108.

Peripherals interface 218 is used to couple input and output peripheralsof the device to CPU 220 and memory 202. The one or more processors 220run or execute various software programs and/or sets of instructionsstored in memory 202 to perform various functions for device 200 and toprocess data. In some embodiments, peripherals interface 218, CPU 220,and memory controller 222 are implemented on a single chip, such as chip204. In some other embodiments, they are implemented on separate chips.

RF (radio frequency) circuitry 208 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 208 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 208 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 208 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 208optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 210, speaker 211, and microphone 213 provide an audiointerface between a user and device 200. Audio circuitry 210 receivesaudio data from peripherals interface 218, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 211.Speaker 211 converts the electrical signal to human-audible sound waves.Audio circuitry 210 also receives electrical signals converted bymicrophone 213 from sound waves. Audio circuitry 210 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 218 for processing. Audio data are retrieved fromand/or transmitted to memory 202 and/or RF circuitry 208 by peripheralsinterface 218. In some embodiments, audio circuitry 210 also includes aheadset jack (e.g., 312, FIG. 3). The headset jack provides an interfacebetween audio circuitry 210 and removable audio input/outputperipherals, such as output-only headphones or a headset with bothoutput (e.g., a headphone for one or both ears) and input (e.g., amicrophone).

I/O subsystem 206 couples input/output peripherals on device 200, suchas touch screen 212 and other input control devices 216, to peripheralsinterface 218. I/O subsystem 206 optionally includes display controller256, optical sensor controller 258, intensity sensor controller 259,haptic feedback controller 261, and one or more input controllers 260for other input or control devices. The one or more input controllers260 receive/send electrical signals from/to other input control devices216. The other input control devices 216 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 260 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 308, FIG.3) optionally include an up/down button for volume control of speaker211 and/or microphone 213. The one or more buttons optionally include apush button (e.g., 306, FIG. 3).

A quick press of the push button disengages a lock of touch screen 212or begin a process that uses gestures on the touch screen to unlock thedevice, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 306)turns power to device 200 on or off. The user is able to customize afunctionality of one or more of the buttons. Touch screen 212 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 212 provides an input interface and an outputinterface between the device and a user. Display controller 256 receivesand/or sends electrical signals from/to touch screen 212. Touch screen212 displays visual output to the user. The visual output includesgraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput correspond to user-interface objects.

Touch screen 212 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 212 and display controller 256 (along with anyassociated modules and/or sets of instructions in memory 202) detectcontact (and any movement or breaking of the contact) on touch screen212 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 212. In an exemplaryembodiment, a point of contact between touch screen 212 and the usercorresponds to a finger of the user.

Touch screen 212 uses LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 212 and display controller 256 detectcontact and any movement or breaking thereof using any of a plurality oftouch sensing technologies now known or later developed, including butnot limited to capacitive, resistive, infrared, and surface acousticwave technologies, as well as other proximity sensor arrays or otherelements for determining one or more points of contact with touch screen212. In an exemplary embodiment, projected mutual capacitance sensingtechnology is used, such as that found in the iPhone® and iPod Touch®from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 212 isanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 212 displays visual output from device 200, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 212 is asdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 212 has, for example, a video resolution in excess of 100dpi. In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user makes contact with touch screen 212using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 200includes a touchpad (not shown) for activating or deactivatingparticular functions. In some embodiments, the touchpad is atouch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is a touch-sensitive surfacethat is separate from touch screen 212 or an extension of thetouch-sensitive surface formed by the touch screen.

Device 200 also includes power system 262 for powering the variouscomponents. Power system 262 includes a power management system, one ormore power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 200 also includes one or more optical sensors 264. FIG. 2A showsan optical sensor coupled to optical sensor controller 258 in I/Osubsystem 206. Optical sensor 264 includes charge-coupled device (CCD)or complementary metal-oxide semiconductor (CMOS) phototransistors.Optical sensor 264 receives light from the environment, projectedthrough one or more lenses, and converts the light to data representingan image. In conjunction with imaging module 243 (also called a cameramodule), optical sensor 264 captures still images or video. In someembodiments, an optical sensor is located on the back of device 200,opposite touch screen display 212 on the front of the device so that thetouch screen display is used as a viewfinder for still and/or videoimage acquisition. In some embodiments, an optical sensor is located onthe front of the device so that the user's image is obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 264 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 264 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 200 optionally also includes one or more contact intensitysensors 265. FIG. 2A shows a contact intensity sensor coupled tointensity sensor controller 259 in I/O subsystem 206. Contact intensitysensor 265 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 265 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 212). In some embodiments, at least one contact intensitysensor is located on the back of device 200, opposite touch screendisplay 212, which is located on the front of device 200.

Device 200 also includes one or more proximity sensors 266. FIG. 2Ashows proximity sensor 266 coupled to peripherals interface 218.Alternately, proximity sensor 266 is coupled to input controller 260 inI/O subsystem 206. Proximity sensor 266 is performed as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 212 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 200 optionally also includes one or more tactile outputgenerators 267. FIG. 2A shows a tactile output generator coupled tohaptic feedback controller 261 in I/O subsystem 206. Tactile outputgenerator 267 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 265 receives tactile feedbackgeneration instructions from haptic feedback module 233 and generatestactile outputs on device 200 that are capable of being sensed by a userof device 200. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 212) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 200) or laterally (e.g., back and forth inthe same plane as a surface of device 200). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 200, opposite touch screen display 212, which is located on thefront of device 200.

Device 200 also includes one or more accelerometers 268. FIG. 2A showsaccelerometer 268 coupled to peripherals interface 218. Alternately,accelerometer 268 is coupled to an input controller 260 in I/O subsystem206. Accelerometer 268 performs, for example, as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 200 optionally includes, in addition to accelerometer(s) 268, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 200.

In some embodiments, the software components stored in memory 202include operating system 226, communication module (or set ofinstructions) 228, contact/motion module (or set of instructions) 230,graphics module (or set of instructions) 232, text input module (or setof instructions) 234, Global Positioning System (GPS) module (or set ofinstructions) 235, Digital Assistant Client Module 229, and applications(or sets of instructions) 236. Further, memory 202 stores data andmodels, such as user data and models 231. Furthermore, in someembodiments, memory 202 (FIG. 2A) or 470 (FIG. 4) stores device/globalinternal state 257, as shown in FIGS. 2A and 4. Device/global internalstate 257 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 212; sensor state, including informationobtained from the device's various sensors and input control devices216: and location information concerning the device's location and/orattitude.

Operating system 226 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 228 facilitates communication with other devicesover one or more external ports 224 and also includes various softwarecomponents for handling data received by RF circuitry 208 and/orexternal port 224. External port 224 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 230 optionally detects contact with touch screen212 (in conjunction with display controller 256) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 230 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 230 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 230 and display controller 256 detect contact on atouchpad.

In some embodiments, contact/motion module 230 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 200). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 230 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 232 includes various known software components forrendering and displaying graphics on touch screen 212 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 232 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 232 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 256.

Haptic feedback module 233 includes various software components forgenerating instructions used by tactile output generator(s) 267 toproduce tactile outputs at one or more locations on device 200 inresponse to user interactions with device 200.

Text input module 234, which is, in some examples, a component ofgraphics module 232, provides soft keyboards for entering text invarious applications (e.g., contacts 237, email 240, IM 241, browser247, and any other application that needs text input).

GPS module 235 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 238 foruse in location-based dialing; to camera 243 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Digital assistant client module 229 includes various client-side digitalassistant instructions to provide the client-side functionalities of thedigital assistant. For example, digital assistant client module 229 iscapable of accepting voice input (e.g., speech input), text input, touchinput, and/or gestural input through various user interfaces (e.g.,microphone 213, accelerometer(s) 268, touch-sensitive display system212, optical sensor(s) 264, other input control devices 216, etc.) ofportable multifunction device 200. Digital assistant client module 229is also capable of providing output in audio (e.g., speech output),visual, and/or tactile forms through various output interfaces (e.g.,speaker 211, touch-sensitive display system 212, tactile outputgenerator(s) 267, etc.) of portable multifunction device 200. Forexample, output is provided as voice, sound, alerts, text messages,menus, graphics, videos, animations, vibrations, and/or combinations oftwo or more of the above. During operation, digital assistant clientmodule 229 communicates with DA server 106 using RF circuitry 208.

User data and models 231 include various data associated with the user(e.g., user-specific vocabulary data, user preference data,user-specified name pronunciations, data from the user's electronicaddress book, to-do lists, shopping lists, etc.) to provide theclient-side functionalities of the digital assistant. Further, user dataand models 231 include various models (e.g., speech recognition models,statistical language models, natural language processing models,ontology, task flow models, service models, etc.) for processing userinput and determining user intent.

In some examples, digital assistant client module 229 utilizes thevarious sensors, subsystems, and peripheral devices of portablemultifunction device 200 to gather additional information from thesurrounding environment of the portable multifunction device 200 toestablish a context associated with a user, the current userinteraction, and/or the current user input. In some examples, digitalassistant client module 229 provides the contextual information or asubset thereof with the user input to DA server 106 to help infer theuser's intent. In some examples, the digital assistant also uses thecontextual information to determine how to prepare and deliver outputsto the user. Contextual information is referred to as context data.

In some examples, the contextual information that accompanies the userinput includes sensor information, e.g., lighting, ambient noise,ambient temperature, images or videos of the surrounding environment,etc. In some examples, the contextual information can also include thephysical state of the device, e.g., device orientation, device location,device temperature, power level, speed, acceleration, motion patterns,cellular signals strength, etc. In some examples, information related tothe software state of DA server 106, e.g., running processes, installedprograms, past and present network activities, background services,error logs, resources usage, etc., and of portable multifunction device200 is provided to DA server 106 as contextual information associatedwith a user input.

In some examples, the digital assistant client module 229 selectivelyprovides information (e.g., user data 231) stored on the portablemultifunction device 200 in response to requests from DA server 106. Insome examples, digital assistant client module 229 also elicitsadditional input from the user via a natural language dialogue or otheruser interfaces upon request by DA server 106. Digital assistant clientmodule 229 passes the additional input to DA server 106 to help DAserver 106 in intent deduction and/or fulfillment of the user's intentexpressed in the user request.

A more detailed description of a digital assistant is described belowwith reference to FIGS. 7A-C. It should be recognized that digitalassistant client module 229 can include any number of the sub-modules ofdigital assistant module 726 described below.

Applications 236 include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 237 (sometimes called an address book or contact        list);    -   Telephone module 238;    -   Video conference module 239;    -   E-mail client module 240;    -   Instant messaging (IM) module 241;    -   Workout support module 242;    -   Camera module 243 for still and/or video images;    -   Image management module 244;    -   Video player module;    -   Music player module;    -   Browser module 247;    -   Calendar module 248;    -   Widget modules 249, which includes, in some examples, one or        more of: weather widget 249-1, stocks widget 249-2, calculator        widget 249-3, alarm clock widget 249-4, dictionary widget 249-5,        and other widgets obtained by the user, as well as user-created        widgets 249-6;    -   Widget creator module 250 for making user-created widgets 249-6;    -   Search module 251;    -   Video and music player module 252, which merges video player        module and music player module;    -   Notes module 253;    -   Map module 254; and/or    -   Online video module 255.

Examples of other applications 236 that are stored in memory 202 includeother word processing applications, other image editing applications,drawing applications, presentation applications, JAVA-enabledapplications, encryption, digital rights management, voice recognition,and voice replication.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, contacts module 237 are used to manage an address book or contactlist (e.g., stored in application internal state 292 of contacts module237 in memory 202 or memory 470), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 238, videoconference module 239, e-mail 240, or IM 241; and so forth.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, contact/motionmodule 230, graphics module 232, and text input module 234, telephonemodule 238 are used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in contactsmodule 237, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication uses any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, optical sensor264, optical sensor controller 258, contact/motion module 230, graphicsmodule 232, text input module 234, contacts module 237, and telephonemodule 238, video conference module 239 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, e-mail client module 240 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 244,e-mail client module 240 makes it very easy to create and send e-mailswith still or video images taken with camera module 243.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, the instant messaging module 241 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, map module 254, and music playermodule, workout support module 242 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data: calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 212, display controller 256, opticalsensor(s) 264, optical sensor controller 258, contact/motion module 230,graphics module 232, and image management module 244, camera module 243includes executable instructions to capture still images or video(including a video stream) and store them into memory 202, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 202.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, text input module 234,and camera module 243, image management module 244 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, browser module 247 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, e-mail client module 240, and browser module 247,calendar module 248 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, widget modules 249 aremini-applications that can be downloaded and used by a user (e.g.,weather widget 249-1, stocks widget 249-2, calculator widget 249-3,alarm clock widget 249-4, and dictionary widget 249-5) or created by theuser (e.g., user-created widget 249-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, the widget creator module 250are used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, search module 251 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 202 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, and browser module 247, video and musicplayer module 252 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 212 or on an external, connected display via externalport 224). In some embodiments, device 200 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, notes module 253 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, and browser module 247, map module 254are used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions, data on stores and other points ofinterest at or near a particular location, and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, text input module 234, e-mail clientmodule 240, and browser module 247, online video module 255 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 224), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 241, rather than e-mail client module 240, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules can be combined or otherwiserearranged in various embodiments. For example, video player module canbe combined with music player module into a single module (e.g., videoand music player module 252, FIG. 2A). In some embodiments, memory 202stores a subset of the modules and data structures identified above.Furthermore, memory 202 stores additional modules and data structuresnot described above.

In some embodiments, device 200 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device200, the number of physical input control devices (such as push buttons,dials, and the like) on device 200 is reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 200 to a main, home, or root menu from any userinterface that is displayed on device 200. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 202 (FIG. 2A) or 470 (FIG. 4) includes event sorter 270 (e.g., inoperating system 226) and a respective application 236-1 (e.g., any ofthe aforementioned applications 237-251, 255, 480-490).

Event sorter 270 receives event information and determines theapplication 236-1 and application view 291 of application 236-1 to whichto deliver the event information. Event sorter 270 includes eventmonitor 271 and event dispatcher module 274. In some embodiments,application 236-1 includes application internal state 292, whichindicates the current application view(s) displayed on touch-sensitivedisplay 212 when the application is active or executing. In someembodiments, device/global internal state 257 is used by event sorter270 to determine which application(s) is (are) currently active, andapplication internal state 292 is used by event sorter 270 to determineapplication views 291 to which to deliver event information.

In some embodiments, application internal state 292 includes additionalinformation, such as one or more of: resume information to be used whenapplication 236-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 236-1, a state queue for enabling the user to go back toa prior state or view of application 236-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 271 receives event information from peripherals interface218. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 212, as part of a multi-touchgesture). Peripherals interface 218 transmits information it receivesfrom I/O subsystem 206 or a sensor, such as proximity sensor 266,accelerometer(s) 268, and/or microphone 213 (through audio circuitry210). Information that peripherals interface 218 receives from I/Osubsystem 206 includes information from touch-sensitive display 212 or atouch-sensitive surface.

In some embodiments, event monitor 271 sends requests to the peripheralsinterface 218 at predetermined intervals. In response, peripheralsinterface 218 transmits event information. In other embodiments,peripherals interface 218 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 270 also includes a hit viewdetermination module 272 and/or an active event recognizer determinationmodule 273.

Hit view determination module 272 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 212 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected is called the hit view,and the set of events that are recognized as proper inputs is determinedbased, at least in part, on the hit view of the initial touch thatbegins a touch-based gesture.

Hit view determination module 272 receives information related to subevents of a touch-based gesture. When an application has multiple viewsorganized in a hierarchy, hit view determination module 272 identifies ahit view as the lowest view in the hierarchy which should handle thesub-event. In most circumstances, the hit view is the lowest level viewin which an initiating sub-event occurs (e.g., the first sub-event inthe sequence of sub-events that form an event or potential event). Oncethe hit view is identified by the hit view determination module 272, thehit view typically receives all sub-events related to the same touch orinput source for which it was identified as the hit view.

Active event recognizer determination module 273 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 273 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 273 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 274 dispatches the event information to an eventrecognizer (e.g., event recognizer 280). In embodiments including activeevent recognizer determination module 273, event dispatcher module 274delivers the event information to an event recognizer determined byactive event recognizer determination module 273. In some embodiments,event dispatcher module 274 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 282.

In some embodiments, operating system 226 includes event sorter 270.Alternatively, application 236-1 includes event sorter 270. In yet otherembodiments, event sorter 270 is a stand-alone module, or a part ofanother module stored in memory 202, such as contact/motion module 230.

In some embodiments, application 236-1 includes a plurality of eventhandlers 290 and one or more application views 291, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 291 of the application 236-1 includes one or more event recognizers280. Typically, a respective application view 291 includes a pluralityof event recognizers 280. In other embodiments, one or more of eventrecognizers 280 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 236-1inherits methods and other properties. In some embodiments, a respectiveevent handler 290 includes one or more of: data updater 276, objectupdater 277, GUI updater 278, and/or event data 279 received from eventsorter 270. Event handler 290 utilizes or calls data updater 276, objectupdater 277, or GUI updater 278 to update the application internal state292. Alternatively, one or more of the application views 291 include oneor more respective event handlers 290. Also, in some embodiments, one ormore of data updater 276, object updater 277, and GUI updater 278 areincluded in a respective application view 291.

A respective event recognizer 280 receives event information (e.g.,event data 279) from event sorter 270 and identifies an event from theevent information. Event recognizer 280 includes event receiver 282 andevent comparator 284. In some embodiments, event recognizer 280 alsoincludes at least a subset of: metadata 283, and event deliveryinstructions 288 (which include sub-event delivery instructions).

Event receiver 282 receives event information from event sorter 270. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation also includes speed and direction of the sub-event. In someembodiments, events include rotation of the device from one orientationto another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 284 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 284 includes eventdefinitions 286. Event definitions 286 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(287-1), event 2 (287-2), and others. In some embodiments, sub-events inan event (287) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (287-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (287-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 212, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 290.

In some embodiments, event definition 287 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 284 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 212, when a touch is detected on touch-sensitivedisplay 212, event comparator 284 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 290, the event comparator uses the result of the hit testto determine which event handler 290 should be activated. For example,event comparator 284 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (287) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 280 determines that the series ofsub-events do not match any of the events in event definitions 286, therespective event recognizer 280 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 280 includes metadata283 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 283 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 283 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 280 activates eventhandler 290 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 280 delivers event information associated with theevent to event handler 290. Activating an event handler 290 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 280 throws a flag associated withthe recognized event, and event handler 290 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 288 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 276 creates and updates data used inapplication 236-1. For example, data updater 276 updates the telephonenumber used in contacts module 237, or stores a video file used in videoplayer module. In some embodiments, object updater 277 creates andupdates objects used in application 236-1. For example, object updater277 creates a new user-interface object or updates the position of auser-interface object. GUI updater 278 updates the GUI. For example, GUIupdater 278 prepares display information and sends it to graphics module232 for display on a touch-sensitive display.

In some embodiments, event handler(s) 290 includes or has access to dataupdater 276, object updater 277, and GUI updater 278. In someembodiments, data updater 276, object updater 277, and GUI updater 278are included in a single module of a respective application 236-1 orapplication view 291. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 200 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions: detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 3 illustrates a portable multifunction device 200 having a touchscreen 212 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 300.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 302 (not drawn to scalein the figure) or one or more styluses 303 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 200. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 200 also includes one or more physical buttons, such as “home” ormenu button 304. As described previously, menu button 304 is used tonavigate to any application 236 in a set of applications that isexecuted on device 200. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen212.

In one embodiment, device 200 includes touch screen 212, menu button304, push button 306 for powering the device on/off and locking thedevice, volume adjustment button(s) 308, subscriber identity module(SIM) card slot 310, headset jack 312, and docking/charging externalport 224. Push button 306 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 200 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 213. Device 200 also, optionally, includes one or morecontact intensity sensors 265 for detecting intensity of contacts ontouch screen 212 and/or one or more tactile output generators 267 forgenerating tactile outputs for a user of device 200.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 400 need not be portable. In some embodiments,device 400 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 400 typically includesone or more processing units (CPUs) 410, one or more network or othercommunications interfaces 460, memory 470, and one or more communicationbuses 420 for interconnecting these components. Communication buses 420optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 400 includes input/output (I/O) interface 430 comprising display440, which is typically a touch screen display. I/O interface 430 alsooptionally includes a keyboard and/or mouse (or other pointing device)450 and touchpad 455, tactile output generator 457 for generatingtactile outputs on device 400 (e.g., similar to tactile outputgenerator(s) 267 described above with reference to FIG. 2A), sensors 459(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 265 describedabove with reference to FIG. 2A). Memory 470 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 470 optionally includes one or more storage devicesremotely located from CPU(s) 410. In some embodiments, memory 470 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 202 of portablemultifunction device 200 (FIG. 2A), or a subset thereof. Furthermore,memory 470 optionally stores additional programs, modules, and datastructures not present in memory 202 of portable multifunction device200. For example, memory 470 of device 400 optionally stores drawingmodule 480, presentation module 482, word processing module 484, websitecreation module 486, disk authoring module 488, and/or spreadsheetmodule 490, while memory 202 of portable multifunction device 200 (FIG.2A) optionally does not store these modules.

Each of the above-identified elements in FIG. 4 is, in some examples,stored in one or more of the previously mentioned memory devices. Eachof the above-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are combined or otherwise rearranged in variousembodiments. In some embodiments, memory 470 stores a subset of themodules and data structures identified above. Furthermore, memory 470stores additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces thatcan be implemented on, for example, portable multifunction device 200.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 200 in accordance withsome embodiments. Similar user interfaces are implemented on device 400.In some embodiments, user interface 500 includes the following elements,or a subset or superset thereof:

Signal strength indicator(s) 502 for wireless communication(s), such ascellular and Wi-Fi signals;

-   -   Time 504;    -   Bluetooth indicator 505;    -   Battery status indicator 506;    -   Tray 508 with icons for frequently used applications, such as:        -   Icon 516 for telephone module 238, labeled “Phone,” which            optionally includes an indicator 514 of the number of missed            calls or voicemail messages;        -   Icon 518 for e-mail client module 240, labeled “Mail,” which            optionally includes an indicator 510 of the number of unread            e-mails;        -   Icon 520 for browser module 247, labeled “Browser;” and        -   Icon 522 for video and music player module 252, also            referred to as iPod (trademark of Apple Inc.) module 252,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 524 for IM module 241, labeled “Messages;”        -   Icon 526 for calendar module 248, labeled “Calendar;”        -   Icon 528 for image management module 244, labeled “Photos;”        -   Icon 530 for camera module 243, labeled “Camera;”        -   Icon 532 for online video module 255, labeled “Online            Video;”        -   Icon 534 for stocks widget 249-2, labeled “Stocks;”        -   Icon 536 for map module 254, labeled “Maps;”        -   Icon 538 for weather widget 249-1, labeled “Weather;”        -   Icon 540 for alarm clock widget 249-4, labeled “Clock;”        -   Icon 542 for workout support module 242, labeled “Workout            Support;”        -   Icon 544 for notes module 253, labeled “Notes;” and        -   Icon 546 for a settings application or module, labeled            “Settings,” which provides access to settings for device 200            and its various applications 236.

It should be noted that the icon labels illustrated in FIG. 5A aremerely exemplary. For example, icon 522 for video and music playermodule 252 is optionally labeled “Music” or “Music Player.” Other labelsare, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 5B illustrates an exemplary user interface on a device (e.g.,device 400, FIG. 4) with a touch-sensitive surface 551 (e.g., a tabletor touchpad 455, FIG. 4) that is separate from the display 550 (e.g.,touch screen display 212). Device 400 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 457) fordetecting intensity of contacts on touch-sensitive surface 551 and/orone or more tactile output generators 459 for generating tactile outputsfor a user of device 400.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 212 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 5B. In some embodiments, the touch-sensitive surface(e.g., 551 in FIG. 5B) has a primary axis (e.g., 552 in FIG. 5B) thatcorresponds to a primary axis (e.g., 553 in FIG. 5B) on the display(e.g., 550). In accordance with these embodiments, the device detectscontacts (e.g., 560 and 562 in FIG. 5B) with the touch-sensitive surface551 at locations that correspond to respective locations on the display(e.g., in FIG. 5B, 560 corresponds to 568 and 562 corresponds to 570).In this way, user inputs (e.g., contacts 560 and 562, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,551 in FIG. 5B) are used by the device to manipulate the user interfaceon the display (e.g., 550 in FIG. 5B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 6A illustrates exemplary personal electronic device 600. Device 600includes body 602. In some embodiments, device 600 includes some or allof the features described with respect to devices 200 and 400 (e.g.,FIGS. 2A-4). In some embodiments, device 600 has touch-sensitive displayscreen 604, hereafter touch screen 604. Alternatively, or in addition totouch screen 604, device 600 has a display and a touch-sensitivesurface. As with devices 200 and 400, in some embodiments, touch screen604 (or the touch-sensitive surface) has one or more intensity sensorsfor detecting intensity of contacts (e.g., touches) being applied. Theone or more intensity sensors of touch screen 604 (or thetouch-sensitive surface) provide output data that represents theintensity of touches. The user interface of device 600 responds totouches based on their intensity, meaning that touches of differentintensities can invoke different user interface operations on device600.

Techniques for detecting and processing touch intensity are found, forexample, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 600 has one or more input mechanisms 606 and608. Input mechanisms 606 and 608, if included, are physical. Examplesof physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 600 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 600 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 600 to be worn by a user.

FIG. 6B depicts exemplary personal electronic device 600. In someembodiments, device 600 includes some or all of the components describedwith respect to FIGS. 2A, 2B, and 4. Device 600 has bus 612 thatoperatively couples I/O section 614 with one or more computer processors616 and memory 618. I/O section 614 is connected to display 604, whichcan have touch-sensitive component 622 and, optionally, touch-intensitysensitive component 624. In addition, I/O section 614 is connected withcommunication unit 630 for receiving application and operating systemdata, using Wi-Fi, Bluetooth, near field communication (NFC), cellular,and/or other wireless communication techniques. Device 600 includesinput mechanisms 606 and/or 608. Input mechanism 606 is a rotatableinput device or a depressible and rotatable input device, for example.Input mechanism 608 is a button, in some examples.

Input mechanism 608 is a microphone, in some examples. Personalelectronic device 600 includes, for example, various sensors, such asGPS sensor 632, accelerometer 634, directional sensor 640 (e.g.,compass), gyroscope 636, motion sensor 638, and/or a combinationthereof, all of which are operatively connected to I/O section 614.

Memory 618 of personal electronic device 600 is a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors616, for example, cause the computer processors to perform thetechniques and processes described below. The computer-executableinstructions, for example, are also stored and/or transported within anynon-transitory computer-readable storage medium for use by or inconnection with an instruction execution system, apparatus, or device,such as a computer-based system, processor-containing system, or othersystem that can fetch the instructions from the instruction executionsystem, apparatus, or device and execute the instructions. Personalelectronic device 600 is not limited to the components and configurationof FIG. 6B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, for example, displayed on thedisplay screen of devices 200, 400, 600, 800, or 900 (FIGS. 2A, 4, 6A-B,8, 9A-F, and 12). For example, an image (e.g., icon), a button, and text(e.g., hyperlink) each constitutes an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 455 in FIG. 4 or touch-sensitive surface 551 in FIG. 5B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 212 in FIG. 2A or touch screen 212in FIG. 5A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of; a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds includesa first intensity threshold and a second intensity threshold. In thisexample, a contact with a characteristic intensity that does not exceedthe first threshold results in a first operation, a contact with acharacteristic intensity that exceeds the first intensity threshold anddoes not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is based ononly a portion of the continuous swipe contact, and not the entire swipecontact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm is applied to theintensities of the swipe contact prior to determining the characteristicintensity of the contact. For example, the smoothing algorithmoptionally includes one or more of: an unweighted sliding-averagesmoothing algorithm, a triangular smoothing algorithm, a median filtersmoothing algorithm, and/or an exponential smoothing algorithm. In somecircumstances, these smoothing algorithms eliminate narrow spikes ordips in the intensities of the swipe contact for purposes of determininga characteristic intensity.

The intensity of a contact on the touch-sensitive surface ischaracterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

3. Digital Assistant System

FIG. 7A illustrates a block diagram of digital assistant system 700 inaccordance with various examples. In some examples, digital assistantsystem 700 is implemented on a standalone computer system. In someexamples, digital assistant system 700 is distributed across multiplecomputers. In some examples, some of the modules and functions of thedigital assistant are divided into a server portion and a clientportion, where the client portion resides on one or more user devices(e.g., devices 104, 122, 200, 400, 600, 800, or 900) and communicateswith the server portion (e.g., server system 108) through one or morenetworks, e.g., as shown in FIG. 1. In some examples, digital assistantsystem 700 is an implementation of server system 108 (and/or DA server106) shown in FIG. 1. It should be noted that digital assistant system700 is only one example of a digital assistant system, and that digitalassistant system 700 can have more or fewer components than shown, cancombine two or more components, or can have a different configuration orarrangement of the components. The various components shown in FIG. 7Aare implemented in hardware, software instructions for execution by oneor more processors, firmware, including one or more signal processingand/or application specific integrated circuits, or a combinationthereof.

Digital assistant system 700 includes memory 702, one or more processors704, input/output (I/O) interface 706, and network communicationsinterface 708. These components can communicate with one another overone or more communication buses or signal lines 710.

In some examples, memory 702 includes a non-transitory computer-readablemedium, such as high-speed random access memory and/or a non-volatilecomputer-readable storage medium (e.g., one or more magnetic diskstorage devices, flash memory devices, or other non-volatile solid-statememory devices).

In some examples, I/O interface 706 couples input/output devices 716 ofdigital assistant system 700, such as displays, keyboards, touchscreens, and microphones, to user interface module 722. I/O interface706, in conjunction with user interface module 722, receives user inputs(e.g., voice input, keyboard inputs, touch inputs, etc.) and processesthem accordingly. In some examples, e.g., when the digital assistant isimplemented on a standalone user device, digital assistant system 700includes any of the components and I/O communication interfacesdescribed with respect to devices 200, 400, 600, 800, or 900 in FIGS.2A, 4, 6A-B, 8. 9A-F, and 12. In some examples, digital assistant system700 represents the server portion of a digital assistant implementation,and can interact with the user through a client-side portion residing ona user device (e.g., devices 104, 200, 400, 600, 800, or 900).

In some examples, the network communications interface 708 includeswired communication port(s) 712 and/or wireless transmission andreception circuitry 714. The wired communication port(s) receives andsend communication signals via one or more wired interfaces, e.g.,Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wirelesscircuitry 714 receives and sends RF signals and/or optical signalsfrom/to communications networks and other communications devices. Thewireless communications use any of a plurality of communicationsstandards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA,Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communicationprotocol. Network communications interface 708 enables communicationbetween digital assistant system 700 with networks, such as theInternet, an intranet, and/or a wireless network, such as a cellulartelephone network, a wireless local area network (LAN), and/or ametropolitan area network (MAN), and other devices.

In some examples, memory 702, or the computer-readable storage media ofmemory 702, stores programs, modules, instructions, and data structuresincluding all or a subset of: operating system 718, communicationsmodule 720, user interface module 722, one or more applications 724, anddigital assistant module 726. In particular, memory 702, or thecomputer-readable storage media of memory 702, stores instructions forperforming the processes described below. One or more processors 704execute these programs, modules, and instructions, and reads/writesfrom/to the data structures.

Operating system 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communications between varioushardware, firmware, and software components.

Communications module 720 facilitates communications between digitalassistant system 700 with other devices over network communicationsinterface 708. For example, communications module 720 communicates withRF circuitry 208 of electronic devices such as devices 200, 400, and 600shown in FIGS. 2A, 4, 6A-B, respectively. Communications module 720 alsoincludes various components for handling data received by wirelesscircuitry 714 and/or wired communications port 712.

User interface module 722 receives commands and/or inputs from a uservia I/O interface 706 (e.g., from a keyboard, touch screen, pointingdevice, controller, and/or microphone), and generate user interfaceobjects on a display. User interface module 722 also prepares anddelivers outputs (e.g., speech, sound, animation, text, icons,vibrations, haptic feedback, light, etc.) to the user via the I/Ointerface 706 (e.g., through displays, audio channels, speakers,touch-pads, etc.).

Applications 724 include programs and/or modules that are configured tobe executed by one or more processors 704. For example, if the digitalassistant system is implemented on a standalone user device,applications 724 include user applications, such as games, a calendarapplication, a navigation application, or an email application. Ifdigital assistant system 700 is implemented on a server, applications724 include resource management applications, diagnostic applications,or scheduling applications, for example.

Memory 702 also stores digital assistant module 726 (or the serverportion of a digital assistant). In some examples, digital assistantmodule 726 includes the following sub-modules, or a subset or supersetthereof: input/output processing module 728, speech-to-text (STT)processing module 730, natural language processing module 732, dialogueflow processing module 734, task flow processing module 736, serviceprocessing module 738, and speech synthesis processing module 740. Eachof these modules has access to one or more of the following systems ordata and models of the digital assistant module 726, or a subset orsuperset thereof: ontology 760, vocabulary index 744, user data 748,task flow models 754, service models 756, and ASR systems 758.

In some examples, using the processing modules, data, and modelsimplemented in digital assistant module 726, the digital assistant canperform at least some of the following: converting speech input intotext; identifying a user's intent expressed in a natural language inputreceived from the user; actively eliciting and obtaining informationneeded to fully infer the user's intent (e.g., by disambiguating words,games, intentions, etc.); determining the task flow for fulfilling theinferred intent; and executing the task flow to fulfill the inferredintent.

In some examples, as shown in FIG. 7B, I/O processing module 728interacts with the user through I/O devices 716 in FIG. 7A or with auser device (e.g., devices 104, 200, 400, or 600) through networkcommunications interface 708 in FIG. 7A to obtain user input (e.g., aspeech input) and to provide responses (e.g., as speech outputs) to theuser input. I/O processing module 728 optionally obtains contextualinformation associated with the user input from the user device, alongwith or shortly after the receipt of the user input. The contextualinformation includes user-specific data, vocabulary, and/or preferencesrelevant to the user input. In some examples, the contextual informationalso includes software and hardware states of the user device at thetime the user request is received, and/or information related to thesurrounding environment of the user at the time that the user requestwas received. In some examples, I/O processing module 728 also sendsfollow-up questions to, and receive answers from, the user regarding theuser request. When a user request is received by I/O processing module728 and the user request includes speech input, I/O processing module728 forwards the speech input to STT processing module 730 (or speechrecognizer) for speech-to-text conversions.

STT processing module 730 includes one or more ASR systems 758. The oneor more ASR systems 758 can process the speech input that is receivedthrough I/O processing module 728 to produce a recognition result. EachASR system 758 includes a front-end speech pre-processor. The front-endspeech pre-processor extracts representative features from the speechinput. For example, the front-end speech pre-processor performs aFourier transform on the speech input to extract spectral features thatcharacterize the speech input as a sequence of representativemulti-dimensional vectors. Further, each ASR system 758 includes one ormore speech recognition models (e.g., acoustic models and/or languagemodels) and implements one or more speech recognition engines. Examplesof speech recognition models include Hidden Markov Models,Gaussian-Mixture Models, Deep Neural Network Models, n-gram languagemodels, and other statistical models. Examples of speech recognitionengines include the dynamic time warping based engines and weightedfinite-state transducers (WFST) based engines. The one or more speechrecognition models and the one or more speech recognition engines areused to process the extracted representative features of the front-endspeech pre-processor to produce intermediate recognitions results (e.g.,phonemes, phonemic strings, and sub-words), and ultimately, textrecognition results (e.g., words, word strings, or sequence of tokens).In some examples, the speech input is processed at least partially by athird-party service or on the user's device (e.g., device 104, 200, 400,or 600) to produce the recognition result. Once STT processing module730 produces recognition results containing a text string (e.g., words,or sequence of words, or sequence of tokens), the recognition result ispassed to natural language processing module 732 for intent deduction.In some examples, STT processing module 730 produces multiple candidatetext representations of the speech input. Each candidate textrepresentation is a sequence of words or tokens corresponding to thespeech input. In some examples, each candidate text representation isassociated with a speech recognition confidence score. Based on thespeech recognition confidence scores, STT processing module 730 ranksthe candidate text representations and provides the n-best (e.g., nhighest ranked) candidate text representation(s) to natural languageprocessing module 732 for intent deduction, where n is a predeterminedinteger greater than zero. For example, in one example, only the highestranked (n=1) candidate text representation is passed to natural languageprocessing module 732 for intent deduction. In another example, the fivehighest ranked (n=5) candidate text representations are passed tonatural language processing module 732 for intent deduction.

More details on the speech-to-text processing are described in U.S.Utility application Ser. No. 13/236,942 for “Consolidating SpeechRecognition Results,” filed on Sep. 20, 2011, the entire disclosure ofwhich is incorporated herein by reference.

In some examples, STT processing module 730 includes and/or accesses avocabulary of recognizable words via phonetic alphabet conversion module731. Each vocabulary word is associated with one or more candidatepronunciations of the word represented in a speech recognition phoneticalphabet. In particular, the vocabulary of recognizable words includes aword that is associated with a plurality of candidate pronunciations.For example, the vocabulary includes the word “tomato” that isassociated with the candidate pronunciations of

and

. Further, vocabulary words are associated with custom candidatepronunciations that are based on previous speech inputs from the user.Such custom candidate pronunciations are stored in STT processing module730 and are associated with a particular user via the user's profile onthe device. In some examples, the candidate pronunciations for words aredetermined based on the spelling of the word and one or more linguisticand/or phonetic rules. In some examples, the candidate pronunciationsare manually generated, e.g., based on known canonical pronunciations.

In some examples, the candidate pronunciations are ranked based on thecommonness of the candidate pronunciation. For example, the candidatepronunciation

is ranked higher than

, because the former is a more commonly used pronunciation (e.g., amongall users, for users in a particular geographical region, or for anyother appropriate subset of users). In some examples, candidatepronunciations are ranked based on whether the candidate pronunciationis a custom candidate pronunciation associated with the user. Forexample, custom candidate pronunciations are ranked higher thancanonical candidate pronunciations. This can be useful for recognizingproper nouns having a unique pronunciation that deviates from canonicalpronunciation. In some examples, candidate pronunciations are associatedwith one or more speech characteristics, such as geographic origin,nationality, or ethnicity. For example, the candidate pronunciation

is associated with the United States, whereas the candidatepronunciation

is associated with Great Britain. Further, the rank of the candidatepronunciation is based on one or more characteristics (e.g., geographicorigin, nationality, ethnicity, etc.) of the user stored in the user'sprofile on the device. For example, it can be determined from the user'sprofile that the user is associated with the United States. Based on theuser being associated with the United States, the candidatepronunciation

(associated with the United States) is ranked higher than the candidatepronunciation

(associated with Great Britain). In some examples, one of the rankedcandidate pronunciations is selected as a predicted pronunciation (e.g.,the most likely pronunciation).

When a speech input is received, STT processing module 730 is used todetermine the phonemes corresponding to the speech input (e.g., using anacoustic model), and then attempt to determine words that match thephonemes (e.g., using a language model). For example, if STT processingmodule 730 first identifies the sequence of phonemes

corresponding to a portion of the speech input, it can then determine,based on vocabulary index 744, that this sequence corresponds to theword “tomato.”

In some examples, STT processing module 730 uses approximate matchingtechniques to determine words in an utterance. Thus, for example, theSTT processing module 730 determines that the sequence of phonemes

corresponds to the word “tomato,” even if that particular sequence ofphonemes is not one of the candidate sequence of phonemes for that word.

Natural language processing module 732 (“natural language processor”) ofthe digital assistant takes the n-best candidate text representation(s)(“word sequence(s)” or “token sequence(s)”) generated by STT processingmodule 730, and attempts to associate each of the candidate textrepresentations with one or more “actionable intents” recognized by thedigital assistant. An “actionable intent” (or “user intent”) representsa task that can be performed by the digital assistant, and can have anassociated task flow implemented in task flow models 754. The associatedtask flow is a series of programmed actions and steps that the digitalassistant takes in order to perform the task. The scope of a digitalassistant's capabilities is dependent on the number and variety of taskflows that have been implemented and stored in task flow models 754, orin other words, on the number and variety of “actionable intents” thatthe digital assistant recognizes. The effectiveness of the digitalassistant, however, also dependents on the assistant's ability to inferthe correct “actionable intent(s)” from the user request expressed innatural language.

In some examples, in addition to the sequence of words or tokensobtained from STT processing module 730, natural language processingmodule 732 also receives contextual information associated with the userrequest, e.g., from I/O processing module 728. The natural languageprocessing module 732 optionally uses the contextual information toclarify, supplement, and/or further define the information contained inthe candidate text representations received from STT processing module730. The contextual information includes, for example, user preferences,hardware, and/or software states of the user device, sensor informationcollected before, during, or shortly after the user request, priorinteractions (e.g., dialogue) between the digital assistant and theuser, and the like. As described herein, contextual information is, insome examples, dynamic, and changes with time, location, content of thedialogue, and other factors.

In some examples, the natural language processing is based on, e.g.,ontology 760. Ontology 760 is a hierarchical structure containing manynodes, each node representing either an “actionable intent” or a“property” relevant to one or more of the “actionable intents” or other“properties.” As noted above, an “actionable intent” represents a taskthat the digital assistant is capable of performing, i.e., it is“actionable” or can be acted on. A “property” represents a parameterassociated with an actionable intent or a sub-aspect of anotherproperty. A linkage between an actionable intent node and a propertynode in ontology 760 defines how a parameter represented by the propertynode pertains to the task represented by the actionable intent node.

In some examples, ontology 760 is made up of actionable intent nodes andproperty nodes. Within ontology 760, each actionable intent node islinked to one or more property nodes either directly or through one ormore intermediate property nodes. Similarly, each property node islinked to one or more actionable intent nodes either directly or throughone or more intermediate property nodes. For example, as shown in FIG.7C, ontology 760 includes a “restaurant reservation” node (i.e., anactionable intent node). Property nodes “restaurant,” “date/time” (forthe reservation), and “party size” are each directly linked to theactionable intent node (i.e., the “restaurant reservation” node).

In addition, property nodes “cuisine,” “price range,” “phone number,”and “location” are sub-nodes of the property node “restaurant,” and areeach linked to the “restaurant reservation” node (i.e., the actionableintent node) through the intermediate property node “restaurant.” Foranother example, as shown in FIG. 7C, ontology 760 also includes a “setreminder” node (i.e., another actionable intent node). Property nodes“date/time” (for setting the reminder) and “subject” (for the reminder)are each linked to the “set reminder” node. Since the property“date/time” is relevant to both the task of making a restaurantreservation and the task of setting a reminder, the property node“date/time” is linked to both the “restaurant reservation” node and the“set reminder” node in ontology 760.

An actionable intent node, along with its linked property nodes, isdescribed as a “domain.” In the present discussion, each domain isassociated with a respective actionable intent, and refers to the groupof nodes (and the relationships there between) associated with theparticular actionable intent. For example, ontology 760 shown in FIG. 7Cincludes an example of restaurant reservation domain 762 and an exampleof reminder domain 764 within ontology 760. The restaurant reservationdomain includes the actionable intent node “restaurant reservation,”property nodes “restaurant,” “date/time,” and “party size,” andsub-property nodes “cuisine,” “price range,” “phone number,” and“location.” Reminder domain 764 includes the actionable intent node “setreminder,” and property nodes “subject” and “date/time.” In someexamples, ontology 760 is made up of many domains. Each domain sharesone or more property nodes with one or more other domains. For example,the “date/time” property node is associated with many different domains(e.g., a scheduling domain, a travel reservation domain, a movie ticketdomain, etc.), in addition to restaurant reservation domain 762 andreminder domain 764.

While FIG. 7C illustrates two example domains within ontology 760, otherdomains include, for example, “find a movie,” “initiate a phone call,”“find directions,” “schedule a meeting,” “send a message,” and “providean answer to a question,” “read a list,” “providing navigationinstructions,” “provide instructions for a task” and so on. A “send amessage” domain is associated with a “send a message” actionable intentnode, and further includes property nodes such as “recipient(s),”“message type,” and “message body.” The property node “recipient” isfurther defined, for example, by the sub-property nodes such as“recipient name” and “message address.”

In some examples, ontology 760 includes all the domains (and henceactionable intents) that the digital assistant is capable ofunderstanding and acting upon. In some examples, ontology 760 ismodified, such as by adding or removing entire domains or nodes, or bymodifying relationships between the nodes within the ontology 760.

In some examples, nodes associated with multiple related actionableintents are clustered under a “super domain” in ontology 760. Forexample, a “travel” super-domain includes a cluster of property nodesand actionable intent nodes related to travel. The actionable intentnodes related to travel includes “airline reservation,” “hotelreservation,” “car rental,” “get directions,” “find points of interest,”and so on. The actionable intent nodes under the same super domain(e.g., the “travel” super domain) have many property nodes in common.For example, the actionable intent nodes for “airline reservation,”“hotel reservation,” “car rental,” “get directions,” and “find points ofinterest” share one or more of the property nodes “start location,”“destination,” “departure date/time,” “arrival date/time,” and “partysize.”

In some examples, each node in ontology 760 is associated with a set ofwords and/or phrases that are relevant to the property or actionableintent represented by the node. The respective set of words and/orphrases associated with each node are the so-called “vocabulary”associated with the node. The respective set of words and/or phrasesassociated with each node are stored in vocabulary index 744 inassociation with the property or actionable intent represented by thenode. For example, returning to FIG. 7B, the vocabulary associated withthe node for the property of “restaurant” includes words such as “food,”“drinks,” “cuisine,” “hungry,” “eat,” “pizza,” “fast food,” “meal,” andso on. For another example, the vocabulary associated with the node forthe actionable intent of “initiate a phone call” includes words andphrases such as “call,” “phone,” “dial,” “ring,” “call this number,”“make a call to,” and so on. The vocabulary index 744 optionallyincludes words and phrases in different languages.

Natural language processing module 732 receives the candidate textrepresentations (e.g., text string(s) or token sequence(s)) from STTprocessing module 730, and for each candidate representation, determineswhat nodes are implicated by the words in the candidate textrepresentation. In some examples, if a word or phrase in the candidatetext representation is found to be associated with one or more nodes inontology 760 (via vocabulary index 744), the word or phrase “triggers”or “activates” those nodes. Based on the quantity and/or relativeimportance of the activated nodes, natural language processing module732 selects one of the actionable intents as the task that the userintended the digital assistant to perform. In some examples, the domainthat has the most “triggered” nodes is selected. In some examples, thedomain having the highest confidence value (e.g., based on the relativeimportance of its various triggered nodes) is selected. In someexamples, the domain is selected based on a combination of the numberand the importance of the triggered nodes. In some examples, additionalfactors are considered in selecting the node as well, such as whetherthe digital assistant has previously correctly interpreted a similarrequest from a user.

User data 748 includes user-specific information, such as user-specificvocabulary, user preferences, user address, user's default and secondarylanguages, user's contact list, and other short-term or long-terminformation for each user. In some examples, natural language processingmodule 732 uses the user-specific information to supplement theinformation contained in the user input to further define the userintent. For example, for a user request “invite my friends to mybirthday party,” natural language processing module 732 is able toaccess user data 748 to determine who the “friends” are and when andwhere the “birthday party” would be held, rather than requiring the userto provide such information explicitly in his/her request.

It should be recognized that in some examples, natural languageprocessing module 732 is implemented using one or more machine learningmechanisms (e.g., neural networks). In particular, the one or moremachine learning mechanisms are configured to receive a candidate textrepresentation and contextual information associated with the candidatetext representation. Based on the candidate text representation and theassociated contextual information, the one or more machine learningmechanisms are configured to determine intent confidence scores over aset of candidate actionable intents. Natural language processing module732 can select one or more candidate actionable intents from the set ofcandidate actionable intents based on the determined intent confidencescores. In some examples, an ontology (e.g., ontology 760) is also usedto select the one or more candidate actionable intents from the set ofcandidate actionable intents.

Other details of searching an ontology based on a token string aredescribed in U.S. Utility application Ser. No. 12/341,743 for “Methodand Apparatus for Searching Using An Active Ontology,” filed Dec. 22,2008, the entire disclosure of which is incorporated herein byreference.

In some examples, once natural language processing module 732 identifiesan actionable intent (or domain) based on the user request, naturallanguage processing module 732 generates a structured query to representthe identified actionable intent. In some examples, the structured queryincludes parameters for one or more nodes within the domain for theactionable intent, and at least some of the parameters are populatedwith the specific information and requirements specified in the userrequest. For example, the user says “Make me a dinner reservation at asushi place at 7.” In this case, natural language processing module 732is able to correctly identify the actionable intent to be “restaurantreservation” based on the user input. According to the ontology, astructured query for a “restaurant reservation” domain includesparameters such as {Cuisine}, {Time}, {Date}, {Party Size}, and thelike. In some examples, based on the speech input and the text derivedfrom the speech input using STT processing module 730, natural languageprocessing module 732 generates a partial structured query for therestaurant reservation domain, where the partial structured queryincludes the parameters {Cuisine=“Sushi”} and {Time=“7 pm”}. However, inthis example, the user's utterance contains insufficient information tocomplete the structured query associated with the domain. Therefore,other necessary parameters such as {Party Size} and {Date} are notspecified in the structured query based on the information currentlyavailable. In some examples, natural language processing module 732populates some parameters of the structured query with receivedcontextual information. For example, in some examples, if the userrequested a sushi restaurant “near me,” natural language processingmodule 732 populates a (location) parameter in the structured query withGPS coordinates from the user device.

In some examples, natural language processing module 732 identifiesmultiple candidate actionable intents for each candidate textrepresentation received from STT processing module 730. Further, in someexamples, a respective structured query (partial or complete) isgenerated for each identified candidate actionable intent. Naturallanguage processing module 732 determines an intent confidence score foreach candidate actionable intent and ranks the candidate actionableintents based on the intent confidence scores. In some examples, naturallanguage processing module 732 passes the generated structured query (orqueries), including any completed parameters, to task flow processingmodule 736 (“task flow processor”). In some examples, the structuredquery (or queries) for the m-best (e.g., m highest ranked) candidateactionable intents are provided to task flow processing module 736,where m is a predetermined integer greater than zero. In some examples,the structured query (or queries) for the m-best candidate actionableintents are provided to task flow processing module 736 with thecorresponding candidate text representation(s).

Other details of inferring a user intent based on multiple candidateactionable intents determined from multiple candidate textrepresentations of a speech input are described in U.S. Utilityapplication Ser. No. 14/298,725 for “System and Method for InferringUser Intent From Speech Inputs,” filed Jun. 6, 2014, the entiredisclosure of which is incorporated herein by reference.

Task flow processing module 736 is configured to receive the structuredquery (or queries) from natural language processing module 732, completethe structured query, if necessary, and perform the actions required to“complete” the user's ultimate request. In some examples, the variousprocedures necessary to complete these tasks are provided in task flowmodels 754. In some examples, task flow models 754 include proceduresfor obtaining additional information from the user and task flows forperforming actions associated with the actionable intent.

As described above, in order to complete a structured query, task flowprocessing module 736 needs to initiate additional dialogue with theuser in order to obtain additional information, and/or disambiguatepotentially ambiguous utterances. When such interactions are necessary,task flow processing module 736 invokes dialogue flow processing module734 to engage in a dialogue with the user. In some examples, dialogueflow processing module 734 determines how (and/or when) to ask the userfor the additional information and receives and processes the userresponses. The questions are provided to and answers are received fromthe users through I/O processing module 728. In some examples, dialogueflow processing module 734 presents dialogue output to the user viaaudio and/or visual output, and receives input from the user via spokenor physical (e.g., clicking) responses. Continuing with the exampleabove, when task flow processing module 736 invokes dialogue flowprocessing module 734 to determine the “party size” and “date”information for the structured query associated with the domain“restaurant reservation,” dialogue flow processing module 734 generatesquestions such as “For how many people?” and “On which day?” to pass tothe user. Once answers are received from the user, dialogue flowprocessing module 734 then populates the structured query with themissing information, or pass the information to task flow processingmodule 736 to complete the missing information from the structuredquery.

Once task flow processing module 736 has completed the structured queryfor an actionable intent, task flow processing module 736 proceeds toperform the ultimate task associated with the actionable intent.Accordingly, task flow processing module 736 executes the steps andinstructions in the task flow model according to the specific parameterscontained in the structured query. For example, the task flow model forthe actionable intent of “restaurant reservation” includes steps andinstructions for contacting a restaurant and actually requesting areservation for a particular party size at a particular time. Forexample, using a structured query such as: {restaurant reservation,restaurant=ABC Café, date=3/12/2012, time=7 pm, party size=5}, task flowprocessing module 736 performs the steps of: (1) logging onto a serverof the ABC Café or a restaurant reservation system such as OPENTABLE®,(2) entering the date, time, and party size information in a form on thewebsite, (3) submitting the form, and (4) making a calendar entry forthe reservation in the user's calendar.

In some examples, task flow processing module 736 employs the assistanceof service processing module 738 (“service processing module”) tocomplete a task requested in the user input or to provide aninformational answer requested in the user input. For example, serviceprocessing module 738 acts on behalf of task flow processing module 736to make a phone call, set a calendar entry, invoke a map search, invokeor interact with other user applications installed on the user device,and invoke or interact with third-party services (e.g., a restaurantreservation portal, a social networking website, a banking portal,etc.). In some examples, the protocols and application programminginterfaces (API) required by each service are specified by a respectiveservice model among service models 756. Service processing module 738accesses the appropriate service model for a service and generatesrequests for the service in accordance with the protocols and APIsrequired by the service according to the service model.

For example, if a restaurant has enabled an online reservation service,the restaurant submits a service model specifying the necessaryparameters for making a reservation and the APIs for communicating thevalues of the necessary parameter to the online reservation service.When requested by task flow processing module 736, service processingmodule 738 establishes a network connection with the online reservationservice using the web address stored in the service model, and sends thenecessary parameters of the reservation (e.g., time, date, party size)to the online reservation interface in a format according to the API ofthe online reservation service.

In some examples, natural language processing module 732, dialogue flowprocessing module 734, and task flow processing module 736 are usedcollectively and iteratively to infer and define the user's intent,obtain information to further clarify and refine the user intent, andfinally generate a response (i.e., an output to the user, or thecompletion of a task) to fulfill the user's intent. The generatedresponse is a dialogue response to the speech input that at leastpartially fulfills the user's intent. Further, in some examples, thegenerated response is output as a speech output. In these examples, thegenerated response is sent to speech synthesis processing module 740(e.g., speech synthesizer) where it can be processed to synthesize thedialogue response in speech form. In yet other examples, the generatedresponse is data content relevant to satisfying a user request in thespeech input.

In examples where task flow processing module 736 receives multiplestructured queries from natural language processing module 732, taskflow processing module 736 initially processes the first structuredquery of the received structured queries to attempt to complete thefirst structured query and/or execute one or more tasks or actionsrepresented by the first structured query. In some examples, the firststructured query corresponds to the highest ranked actionable intent. Inother examples, the first structured query is selected from the receivedstructured queries based on a combination of the corresponding speechrecognition confidence scores and the corresponding intent confidencescores. In some examples, if task flow processing module 736 encountersan error during processing of the first structured query (e.g., due toan inability to determine a necessary parameter), the task flowprocessing module 736 can proceed to select and process a secondstructured query of the received structured queries that corresponds toa lower ranked actionable intent. The second structured query isselected, for example, based on the speech recognition confidence scoreof the corresponding candidate text representation, the intentconfidence score of the corresponding candidate actionable intent, amissing necessary parameter in the first structured query, or anycombination thereof.

Speech synthesis processing module 740 is configured to synthesizespeech outputs for presentation to the user. Speech synthesis processingmodule 740 synthesizes speech outputs based on text provided by thedigital assistant. For example, the generated dialogue response is inthe form of a text string. Speech synthesis processing module 740converts the text string to an audible speech output. Speech synthesisprocessing module 740 uses any appropriate speech synthesis technique inorder to generate speech outputs from text, including, but not limited,to concatenative synthesis, unit selection synthesis, diphone synthesis,domain-specific synthesis, formant synthesis, articulatory synthesis,hidden Markov model (HMM) based synthesis, and sinewave synthesis. Insome examples, speech synthesis processing module 740 is configured tosynthesize individual words based on phonemic strings corresponding tothe words. For example, a phonemic string is associated with a word inthe generated dialogue response. The phonemic string is stored inmetadata associated with the word. Speech synthesis processing module740 is configured to directly process the phonemic string in themetadata to synthesize the word in speech form.

In some examples, instead of (or in addition to) using speech synthesisprocessing module 740, speech synthesis is performed on a remote device(e.g., the server system 108), and the synthesized speech is sent to theuser device for output to the user. For example, this can occur in someimplementations where outputs for a digital assistant are generated at aserver system. And because server systems generally have more processingpower or resources than a user device, it is possible to obtain higherquality speech outputs than would be practical with client-sidesynthesis.

Additional details on digital assistants can be found in the U.S.Utility application Ser. No. 12/987,982, entitled “Intelligent AutomatedAssistant,” filed Jan. 10, 2011, and U.S. Utility application Ser. No.13/251,088, entitled “Generating and Processing Task Items ThatRepresent Tasks to Perform,” filed Sep. 30, 2011, the entire disclosuresof which are incorporated herein by reference.

4. Voice Identification in Digital Assistant Systems

FIGS. 8, 9A-F, 10A-H, and 11A-B illustrate exemplary processes and userinteractions with an electronic device. These figures illustrate someexample processes described below, including the processes 1300 and 1400of FIGS. 13A-G and 14A-E, respectively.

Although some processes below are described as being performed byparticular devices (e.g., device 800, 900), in some examples, theprocesses are performed using a client-server system (e.g., system 100),where devices 800 and/or 900 are implemented as client device(s) incommunication with a server, e.g., as shown in FIG. 1. In some examples,the processes are divided up in any manner between the client device andthe server. In some examples, the processes are performed only by theclient device, or only by multiple client devices (e.g., 800, 900).

The processes described below are performed using software, hardware, ora combination of software and hardware to carry out the principlesdescribes herein. The hardware and software components may bedistributed in any manner between the device(s) and/or system(s)performing the processes (e.g., 800, 900, 100). For example, theprocesses are optionally implemented as computer-executable instructionsstored in memory 702 and/or using digital assistant system 700, or anycomponent thereof, operating on the device(s) and/or system(s)performing the processes. One of skill in the art will understand howother processes are performed using the components of FIGS. 1-4, 6A-B,7A-C.

FIG. 8 illustrates a user interaction with electronic device 800,according to some examples. Device 800 includes the modules andfunctions of a digital assistant described above in FIGS. 7A-C. Device800 is, for example, the same as or similar to device 400 or 600discussed above. In the example of FIG. 8, device 800 is a smartspeaker. However, device 800 may be any type of device, such as a phone,laptop computer, desktop computer, tablet, wearable device (e.g., smartwatch), television, speaker, or any combination thereof.

Device 800 receives a natural language speech input (e.g., from a user)and provides a response to the speech input. According to the techniquesdiscussed below, the response is personalized for a user identifiedbased on the received speech input. For example, FIG. 8 shows a user(e.g., Stephen) providing the speech input “Hey Siri, read my messages”to the device (e.g., to a digital assistant operating on the device).The digital assistant identifies the user based on the received speechinput and provides the personalized response “ok Stephen, reading yourmessages: first message: Corey says meeting at 2 o'clock.”

In some examples, device 800 receives, from external electronicdevice(s), a plurality of speaker profiles for a plurality of users(e.g., registered users). In some examples, the plurality of speakerprofiles are received before receiving speech input based on which auser is identified. In some examples, the registered users form a groupof mutually associated users such as users in the same family, usersregistered in a particular software application, a user-defined group ofusers, or a combination or sub-combination thereof. Thus, in someexamples, the external electronic device(s) are the respectiveelectronic devices of each user of the registered users. For example,when a family includes four users, the external electronic devices arethe four respective electronic devices (e.g., phones, laptops, watches,tablets) of each user in the family. Thus, in some examples, the fourelectronic devices each send a speaker profile for their respective userto device 800.

In the example of FIG. 8, device 800 has received a speaker profile forthe user (e.g., Stephen) from external electronic device 900 (e.g.Stephen's phone). In some examples, device 900 is the same as or similarto device 400 or 600 and is a phone, laptop computer, desktop computer,tablet, wearable device (e.g., smart watch), television, speaker, or anycombination thereof. In some examples, device 900 includes the modulesand functions of a digital assistant, discussed above with respect toFIGS. 7A-C. Device 800 has also received a speaker profile for anotheruser (e.g., Stephen's friend Corey) from an external electronic deviceof the another user (e.g., Corey's device, not shown). Device 800identifies users using the received speaker profiles according to thetechniques discussed below.

In some examples, each speaker profile of the plurality of receivedspeaker profiles includes a plurality of representations of the voice ofa respective user. In some examples, at least one of the plurality ofrepresentations is determined based on an utterance of the respectiveuser. In some examples, the utterance is received at an externalelectronic device (e.g., external to device 800) associated with therespective user. In some examples, the utterance includes a triggerphrase for triggering a digital assistant such as “Hey Siri” or “wakeup.” In some examples, the utterance is spoken by the respective user aspart of an enrollment session for a digital assistant, e.g., anenrollment session where the user utters a trigger phrase a few times toenroll in a voice trigger system for a digital assistant.

In some examples, a digital assistant operating on the external device(e.g., device 900) determines a representation of a received utteranceaccording to the techniques discussed herein. In some examples, thedetermined representation is included in a speaker profile for arespective user. In some examples, the digital assistant operating onthe external device causes the determined representation (and/or speakerprofile) to be sent to another device (e.g., device 800).

For example, Stephen's speaker profile received by device 800 includesmultiple representations of Stephen's voice. The multiplerepresentations are determined based on Stephen's utterances of “HeySiri” at device 900. A digital assistant operating on device 900 causesthe multiple representations forming Stephen's speaker profile to besent to device 800.

In some examples, a representation of an utterance includes a determinedembedding of the utterance. In some examples, the embedding includes avector (e.g., a set of numerical values) representing the voice of auser. In some examples, the embedding is determined using a speakermodel, e.g., implemented as executable instructions stored in thememor(ies) of devices 800 and/or 900. In some examples, the speakermodel includes neural network(s), Hidden Markov Model(s), and/or othermodels known in the art for speaker identification and is trained todetermine embeddings based on received utterances (e.g., speech input).In some examples, the speaker model is trained to determine embeddingsthat emphasize speaker specific characteristics while deemphasizingenvironmental and semantic factors (e.g., environmental noise, theparticular words spoken) and variations in a particular speaker's voice(e.g., the speaker's tired voice, the speaker's angry voice, and thelike). In some examples, the speaker model is trained to determineembeddings that minimize variability for the same speaker (e.g.,embeddings of utterances from the same speaker are the same or similar)while maximizing variability between speakers (e.g., embeddings ofutterances from different speakers are different). In this manner, adetermined embedding may accurately represent a particular speaker'svoice. The determined embedding can thus be compared to other embeddings(e.g., for the particular speaker and for other speakers) to identify aspeaker. For example, if a first embedding is close (e.g., within apredefined threshold as measured by a cosine distance between vectors)to a second embedding representing a particular speaker's voice, thenthe utterance corresponding to the first embedding is likely receivedfrom the particular speaker.

In some examples, a speaker model is trained using utterances of varioususers (e.g., younger users, older users, male users, female users). Insome examples, the utterances of the various users are received atvarious electronic devices such as phones, computers, speakers, andtablet devices. Training the speaker model based on such utterances canallow the speaker model to determine an accurate and robust embedding torepresent a voice of a speaker. In particular, because the sameutterance can have different characteristics when recorded by differenttypes of electronic devices (e.g., due to different device microphoneconfigurations/types), it can be advantageous to train the speaker modelto determine an accurate embedding of an utterance, regardless of thedevice at which the utterance is received.

In some examples, a speaker model is trained using utterances of variousphrases (e.g., “Hey Siri,” “set a timer,” “what's the weather today?”).This may allow determination of accurate embeddings for a variety ofutterances. For example, the speaker model may be initially trainedbased on utterances of “Hey Siri,” but further training using otherutterances may allow the speaker model to accurately determineembeddings for a variety of utterances (e.g., “call my mom”). In thismanner, a user can be identified based on spoken utterances (e.g., “callmy mom”) different from the utterances used to train the speaker model(e.g., “Hey Siri”). Exemplary speaker models and techniques for trainingspeaker models are discussed in:

-   “Personalized Hey Siri.” Apple Machine Learning Journal, vol. 1, no.    9, April 2018; and-   E. Marchi, S. Shum, K. Hwang, S. Kajarekar, S. Sigtia, H.    Richards, R. Haynes, Y. Kim, and J. Bridle. “Generalised    Discriminative Transform via Curriculum Learning for Speaker    Recognition.” Proceedings of the IEEE International Conference on    Acoustics, Speech, and Signal Processing (ICASSP), April 2018.    The contents of these publications are hereby incorporated by    reference in their entireties.

In some examples, device 800 determines, based on comparing receivednatural language speech input to a plurality of speaker profiles, aplurality of likelihoods that the speech input respectively correspondsto a plurality of users (e.g., registered users). In some examples, eachlikelihood of the plurality of likelihoods includes a score (e.g., anumerical value) indicating a degree of match between the receivedspeech input and a respective speaker profile. For example, in FIG. 8,device 800 determines a first likelihood that the speech inputcorresponds to Stephen based on comparing the speech input to Stephen'sspeaker profile and determines a second likelihood that the speech inputcorresponds to Corey based on comparing the speech input to Corey'sspeaker profile. The second likelihood is less than the firstlikelihood, indicating that device 800 is more confident that the speechinput corresponds to Stephen.

In some examples, determining a likelihood that speech input correspondsto a user includes comparing a representation of the speech input toeach of a plurality of representations of the voice of the user. Forexample, device 800 determines a representation (e.g., embedding) of thespeech input and compares the determined embedding to each of aplurality of (e.g., 40) embeddings included in the user's speakerprofile. For example, for each of the plurality of embeddings, device800 computes a distance metric (e.g., normalized cosine distance)between the respective embedding and the determined embedding. Device800 then averages the determined distance metrics to calculate anaverage score indicating the degree of match between the speech inputand a user's speaker profile. In some examples, device 800 thendetermines a likelihood that the speech input corresponds to the userbased on the average score.

In some examples, device 800 determines whether a likelihood that speechinput corresponds to a user exceeds (or does not exceed) one or morethresholds. For example, device 800 determines whether the likelihoodexceeds a first threshold (e.g., an upper threshold). In some examples,a likelihood exceeding the upper threshold indicates high confidencethat the speech input corresponds to the user represented by thelikelihood. In some examples, device 800 determines whether thelikelihood is below a second threshold (e.g., a lower threshold). Insome examples, a likelihood below the lower threshold indicates lowconfidence that the speech input corresponds to the user. In someexamples, device 800 determines whether the likelihood is between twothresholds, such as a lower and an upper threshold. In some examples, alikelihood between two thresholds indicates medium confidence that thespeech input corresponds to the user. In the example of FIG. 8, device800 determines that the likelihood that the speech input corresponds toStephen exceeds the upper threshold. Device 800 determines that thelikelihood that the speech input corresponds to Corey is below the lowerthreshold.

In some examples, device 800 determines whether a likelihood that speechinput corresponds to a first user and a likelihood that speech inputcorresponds to a second user are within a threshold (e.g., a differencethreshold). In some examples, having the first and the secondlikelihoods within the difference threshold means that device 800 cannotdistinguish the first user from the second user with sufficientconfidence (e.g., because the likelihoods are close together). In someexamples, having the first and the second likelihoods not within thedifference threshold means that device 800 can distinguish the users(e.g., because the likelihoods are far apart). In the example of FIG. 8,device 800 determines that the likelihood that the speech inputcorresponds to Stephen and the likelihood that the speech inputcorresponds to Corey are not within the score difference threshold,e.g., meaning that device 800 has distinguished Stephen's voice fromCorey's voice.

In some examples, device 800 determines that a natural language speechinput corresponds to a user (e.g., identifies a user). In some examples,identifying a user includes determining representations of speechinputs, determining likelihoods, determining whether a likelihood thatthe speech input corresponds to the user exceeds or does not exceed oneor more thresholds (e.g., an upper threshold, a lower threshold),determining that the likelihood is higher or lower than otherlikelihoods, and determining that the likelihood is not within adifference threshold of any other determined likelihoods, or acombination or sub-combination thereof. For example, device 800identifies Stephen because the likelihood that the speech input “HeySiri, read my messages” corresponds to Stephen exceeds an upperthreshold, because the likelihood that the speech input corresponds toStephen is the highest determined likelihood, and/or because thelikelihood that the speech input corresponds to Stephen and thelikelihood that the speech input corresponds to Corey are not within adifference threshold.

In some examples, identifying a user includes determining possibleusers, e.g., a number of possible users, corresponding to a speechinput. In some examples, possible users are determined from theregistered users of device 800. In some examples, possible users includeusers who device 800 has at least low, medium, or high confidence in. Insome examples, possible users include users who device 800 cannotdistinguish with sufficient confidence. For example, if device 800 ishighly confident that speech input corresponds to both Corey andStephen, and cannot distinguish Corey from Stephen, Corey and Stephenare determined as two possible users.

In some examples, one or more possible users are non-registered users,e.g., users for which device 800 has not received respective speakerprofiles. In some examples, a non-registered user is determined as apossible user when device 800 determines a high, medium or lowconfidence that the speech input corresponds to a non-registered user.For example, device 800 stores a speaker profile for a non-registereduser, e.g., a generic human speaker profile, and determines a high,medium, or low confidence that speech input corresponds to thenon-registered user.

In some examples, in accordance with identifying a user, device 800provides a response to the speech input, e.g., using I/O processingmodule 728. In some examples, the response to the speech input ispersonalized for the identified user. For example, the response isdetermined based on the identified user's personal information, furtherdiscussed below with respect to FIG. 12. In some examples, providing aresponse to a speech input includes determining a user intent based onthe speech input (e.g. using natural language processing module 732),determining a task based on the user intent (e.g., using task flowprocessing module 736), and providing a result based on the task (e.g.,using input/output processing module 728). Further details regardingproviding personalized responses are discussed below with respect toFIG. 12.

In some examples, a response to a speech input includes one or morewords indicative of personalization for an identified user. For example,the response includes a name of the identified user and/or words/phrasessuch as “your,” “personal,” “personalized,” or “just for you.” This mayadvantageously indicate that a device has correctly (or incorrectly)identified a user. For example, in FIG. 8, device 800 identifies Stephenand provides a response personalized for Stephen, “ok Stephen readingyour messages: first message: Corey says meeting at 2'o clock.”

Sometimes, repeatedly providing the name of a user, e.g., responsive toevery user speech input, may be undesirable, as this may annoy a userand extend the length of device outputs. Accordingly, in some examples,device 800 provides the name of an identified user in a response to thespeech input from which the user is initially identified, but does notprovide the name in subsequent responses to subsequent speech inputsfrom the same user. For example, after device 800 provides thepersonalized response “okay Stephen reading your messages,” Stephenprovides another speech input (e.g., “Hey Siri, call mom”) to device800. Device 800 still identifies Stephen according to the techniquesdiscussed herein, but does not provide a response including the name ofStephen. Rather, device 800 responds “Ok, calling Mom,” for example.However, had the speech input (e.g., “Hey Siri, call mom”) been providedby another user (e.g., Corey), the response to the speech input mayinclude the name of the another user (e.g., “Ok Corey, calling mom”).

In some examples, in accordance with identifying a user, device 800updates a speaker profile for the identified user based on the speechinput. For example, device 800 determines an embedding for the utterance(e.g., using a speaker model) and adds the determined embedding to theparticular user's speaker profile. For example, device 800 determines anembedding of “Hey Siri, read my messages” and adds the embedding toStephen's speaker profile.

Updating the speaker profile in this manner may improve useridentification based on future speech inputs. For example, because morerepresentations of a user's voice (e.g., embeddings) may be included inthe updated speaker profile, the updated speaker profile may be used tomore accurately identify the user. Further, the added representation maymore accurately represent the user's voice when received by device 800than other representations in the user's speaker profile (e.g., becausethe other representations may be determined based on utterances receivedat a device different from device 800, as discussed above).

In some examples, after (or while) providing a personalized response tospeech input, device 800 receives an input (e.g., user speech input)indicative of a recognition error. Exemplary inputs indicative of arecognition error include “that's not me,” “no, stop,” “I'm someoneelse,” and the like. In some examples, in accordance with receiving theinput indicative of a recognition error, device 800 terminates theprovision of the personalized response and/or forgoes updating a speakerprofile of an identified user. In some examples, in accordance withreceiving the input indicative of a recognition error, device 800determines information indicating that the determined representation ofthe initial speech input is incorrect for an (incorrectly) identifieduser. In some examples, such information is used to train a speakermodel to determine more accurate representations of speech input.

For example, if device 800 responds “ok Corey reading your messages . .. ” responsive to Stephen's speech input “Hey Sin, read my messages,”Stephen then provides the input “that's not me.” In accordance withreceiving such input, device 800 terminates the provision of “ok Coreyreading your messages . . . ” and does not update Corey's speakerprofile based on a representation of the utterance “Hey Siri, read mymessages” (because it was actually spoken by Stephen).

In some examples, device 800 determines a user intent associated withreceived natural language speech input (e.g., using natural languageprocessing module 732). In some examples, device 800 determines whethera user intent includes (e.g., is) a type of user intent of a pluralityof types of user intent (e.g., using natural language processing module732). In some examples, the plurality of types of user intent include apersonal intent, a semi-personal intent, and a non-personal intent. Asdiscussed below, the manner in which device 800 interacts with a user(and whether user identification is performed) can depend on thedetermined type of intent.

In some examples, a personal intent includes an intent for which useridentification is required to provide a personalized response. Exemplarypersonal intents include intents of:

-   -   retrieving communications (e.g., emails, text messages, instant        messages, voicemail) (e.g., associated with the inputs “read my        messages,” “read my emails from Corey”);    -   sending communications (e.g., emails, phone calls, text        messages, instant messages) to a personal contact (e.g.,        associated with the input “call mom”),    -   user identification (e.g., associated with the input “who am        I?”);    -   retrieving and/or modifying contact information, recent caller        information, health information, financial information, or a        combination thereof (e.g., associated with the inputs “get me        Corey's contact information,” “how many calories did I burn        today?”, “pay Corey twenty dollars”);    -   retrieving and/or modifying calendar and/or reminder information        (e.g., associated with the inputs “add an appointment to my        calendar,” “remind me to call mom”);    -   retrieving and/or modifying a user's notes and/or lists (e.g.,        user-created text memos, voice memos) (e.g., associated with the        input of “create a new note,” “add this to my shopping list”);    -   activating and/or deactivating security features of a user's        residence (e.g., associated with the inputs “unlock my door,”        “arm my alarm”);    -   modifying a user's personal media account (e.g., associated with        the inputs “add this to my playlist,” “buy ‘thank u next’ by        Ariana Grande,” “subscribe to CNN news”);    -   locating a user's electronic devices (e.g., associated with the        inputs of “find my phone,” “where is my watch?”); and    -   initiating a personalized voice shortcut command (e.g.,        associated with user-defined inputs causing a digital assistant        to perform user-defined task(s)).        Exemplary techniques for personalized voice shortcut commands        are discussed in U.S. patent application Ser. No. 16/146,963,        entitled “ACCELERATED TASK PERFORMANCE,” filed Sep. 28, 2018.

In some examples, a semi-personal intent includes an intent for whichuser identification may be desirable, but may not be required to providea response. Exemplary semi-personal intents include an intent of playingmedia (e.g., associated with the input of “play ‘thank u next’ by ArianaGrande”), an intent of providing the news (e.g., associated with theinput of “what's the news?”), and the like. For example, useridentification may be desirable for semi-personal intents to play anidentified user's favorite version of requested media (or provide newsfrom an identified user's preferred news source), but may not benecessary because a device can provide the requested media (or providethe news) without identifying a user.

In some examples, a non-personal intent includes an intent for whichuser identification is not required (or not even desirable) to provide aresponse. Exemplary non-personal intents include intents of:

-   -   retrieving weather information (e.g., associated with the input        “what's the weather today?”);    -   retrieving sports information (e.g., associated with the input        “did the Patriots win?”);    -   setting a timer, alarm, and/or stopwatch (e.g., associated with        the input “set a timer for 15 minutes”);    -   adjusting media playback (e.g., associated with the inputs “turn        down the volume,” “pause,” “stop,” “rewind”);    -   performing information searches (e.g., associated with the        inputs “search for bars in Hong Kong,” “search Wikipedia for        Abraham Lincoln”);    -   navigation (e.g., associated with the inputs “take me to        Cupertino,” “where is the Golden Gate Bridge?”); and    -   adjusting certain device settings (e.g., associated with the        input “turn up the display brightness”).

Although some intents are described above as being a particular type ofintent (e.g., personal, semi-personal, non-personal), in other examples,the intents can be a different type of intent. For example, an intent ofretrieving sports information can be a semi-personal intent (e.g., toprovide sports information from an identified user's favorite sportscontent provider) instead of a non-personal intent. As another example,an intent of playing media can be a personal intent (e.g., if the speechinput is “play me my music”) instead of a semi-personal intent. Thus, insome examples, the intents discussed above may not be limited to thetypes to which they are initially assigned, as they may vary dependingon the content of the associated speech input and/or if personalizedresponses can be provided for the intents.

In some examples, device 800 determines, for each user, a frequency ofidentification. In some examples, device 800 provides a responsepersonalized for a most frequently identified user when a user cannot beaffirmatively identified. For example, a user cannot be affirmativelyidentified when there is low or medium confidence that speech inputcorresponds to the user and/or the user cannot be distinguished fromother users. For example, if device 800 determines that multiplepossible users correspond to a speech input, device 800 provides aresponse to the speech input personalized for the most frequentlyidentified user of the possible users. In some examples, device 800operates in such manner in accordance with determining that a currentspeech input is associated with a semi-personal intent. For example, ifa user says to device 800 “play the latest news in sports” and device800 has a low confidence that the speech input corresponds to the user(and even lower confidence that the speech input corresponds to otherusers), device 800 provides a response personalized for the mostfrequently identified user. For example, device 800 provides the latestsports news from the most frequently identified user's favorite sportsnews provider.

In some examples, device 800 determines a most recently identified user.In some examples, device 800 provides a response personalized for a mostrecently identified user when a user cannot be affirmatively identified.For example, if device 800 determines that multiple possible userscorrespond to a speech input, device 800 provides a response to thespeech input personalized for the most recently identified user (if heor she is a possible user). In some examples, device 800 operates insuch manner in accordance with determining that a current speech inputis associated with a semi-personal intent. For example, if a user saysto device 800 “play music” and device 800 has a low confidence that thespeech input corresponds to the user (and even lower confidence that thespeech input corresponds to other users), device 800 provides a responsepersonalized for the most recently identified user. For example, device800 plays music from a media collection associated with the mostrecently identified user.

Sometimes, users engage in multi-turn interactions with a digitalassistant operating on device 800. In some examples, a multi-turninteraction includes an interaction where multiple exchanges with thedigital assistant may be required to perform a requested task. Forexample, a user saying “send a message” to device 800, device 800responding “to whom shall I send your message?”, the user then saying“to John, telling him that I'll be late,” and device 800 responding “ok,I sent the message,” is a multi-turn interaction. In some examples, amulti-turn interaction includes an interaction where a user providesmultiple related requests to a digital assistant, e.g., within a shortduration such as 5, 10, 15, or 30 seconds. For example, a user saying“what's the weather in New York?” to device 800, the device respondingit's “70 degrees and sunny,” the user then saying “how about in Paris?”,and the device responding “56 degrees and raining”, is a multi-turninteraction.

In some examples, device 800 only determines whether the first speechinput of a multi-turn interaction corresponds to a user. In otherexamples, device 800 determines whether each speech input (or a subsetof the speech inputs) of a multi-turn interaction corresponds to a sameuser. In some examples, device 800 operates in such manner in accordancewith determining that a user intent associated with a speech input(e.g., first speech input) includes a personal intent. For example,suppose Stephen says to device 800 “send a message to Corey” (associatedwith a personal intent), device 800 responds “what should I say toCorey?”, and Stephen responds “I'll be late.” Device 800 determineswhether each speech input of the multi-turn interaction corresponds tothe same user.

In some examples, if a subsequent speech input in a multi-turninteraction is determined to not correspond to a same user, device 800identifies a user according to the below discussed methods beforeproviding further response. For example, a subsequent speech input doesnot correspond to the same user if there is low confidence that thesubsequent speech input corresponds to the same user. For example, if inthe above interaction, a non-registered user (instead of Stephen) said“I'll be late,” device 800 may output “you'll have to send that messageusing your phone.” In this manner, device 800 can monitor for consistentuser identity through multi-turn interactions, e.g., for interactionsassociated with personal intents, where user identification may bedesirable.

In some examples, device 800 identifies a user using techniques otherthan identifying the user based on the initial speech input, e.g., “HeySiri, read my messages.” For example, device 800 may identify a userusing other techniques in accordance with determining that it has mediumor low confidence in a particular user and/or that the user cannot bedistinguished from other users. As discussed below with respect to FIGS.9A-F, the other technique(s) used to identify a user can depend on atype of user intent, a content of the speech input, and/or a confidencethat a user has been identified. Exemplary other techniques foridentifying a user are now discussed.

In some examples, other techniques for identifying a user includeproviding an output indicative of a request for user identity (e.g.,spoken output, displayed output) and identifying a user based on his/herresponse to the output. In some examples, an output indicative of arequest for user identity includes a request for a user to identifyhim/herself, e.g., “who are you?”, “please tell me who you are.” In someexamples, an output indicative of a request for user identity includes arequest for the user to confirm his/her identity, e.g., “are youStephen?,” “you are Stephen, right?”. In some examples, an outputindicative of a request for user identity requests user disambiguationbetween two or more registered users, e.g., “are you Stephen or Corey?”

In some examples, in response to providing an output indicative of arequest for user identity, device 800 receives a speech input (e.g.,natural language speech input). In some examples, device 800 determineswhether the speech input corresponds to a user. In some examples, ifdevice 800 determines that the speech input corresponds to a user,device 800 identifies that user.

In some examples, if device 800 requests a user to identify his/herself(e.g., asks “please tell me who you are?”) a user provides a speechinput including his/her name (e.g., says “I am Stephen”). In someexamples, device 800 then determines whether the speech inputcorresponds to a user. For example, device 800 processes the speechinput according to the above discussed techniques (e.g., determining alikelihood score, etc.) to determine whether the speech inputcorresponds to a user. As another example, device 800 determines whetherthe speech input includes a name of a user (e.g., using module 730and/or 732). For example, in FIGS. 10A and 10B, a user says “read mymessages” to device 800. Device 800 is unable to distinguish the userfrom other registered users, and thus outputs “please tell me who youare.” The user then responds “I am Stephen,” and device 800 identifiesStephen based on the speech input.

In some examples, if device 800 requests a user to confirm his/heridentity (e.g., asks “you are Stephen, right?”), a user provides aspeech input including an affirmative or negative response. In someexamples, device 800 then determines that the speech input correspondsto a user by determining that the speech input includes an affirmativeresponse (e.g., “yes,” “I am,” “mhmm,” and the like). In some examples,device 800 determines that the speech input does not correspond to auser by determining that the speech input includes a negative response,or otherwise non-affirmative response (e.g., “no,” “I am not,” and thelike).

In some examples, if device 800 requests user disambiguation between twoor more registered users (e.g., “are you Stephen or Corey?”), a userprovides a speech input including a disambiguation (e.g., “I amStephen”). In some examples, device 800 determines that the speech inputcorresponds to a user by determining that the speech input includes aname of the user.

In some examples, providing an output indicative of a request for useridentity includes causing an external electronic device to provide theoutput. In some examples, the output includes a confirmation request toconfirm an action included in the initial speech input (e.g., readingmessages). In some examples, device 800 further outputs a request for auser to confirm the confirmation request (e.g., via audio output ordisplayed output). For example, as shown in FIG. 10C, a user says “readmy messages” to device 800. Device 800 then causes device 900 (e.g., theexternal electronic device associated with the user) to provide thedisplayed output “read your messages?” along with the selectable options“yes” and “no.” Device 800 further outputs “please confirm on yourphone.”

In some examples, an external electronic device receives userconfirmation of the confirmation request. In some examples, userconfirmation of the confirmation request is received via a display ofthe external device (e.g., a user taps the selectable “Yes” option inFIG. 10C), via audio input at the external device (e.g., a user responds“yes” to the request “read your messages?”), and/or via a button inputat the external device. In some examples, the external device sends anindication of user confirmation of the confirmation request to anotherdevice. For example, device 900 sends an indication of user confirmationof the confirmation request to device 800, and device 800 receives theindication of user confirmation of the confirmation request.

In some examples, in accordance with receiving an indication of userconfirmation of a confirmation request, device 800 determines thatspeech input corresponds to the user confirming the confirmationrequest. For example, after the user selects “yes” in FIG. 10C device800 identifies the user who said “read my messages” (e.g., the user ofdevice 900). In this manner, a user can confirm his or her identityusing his or her external electronic device and device 800 can identifythe user.

FIGS. 9A-F illustrate a flowchart of process 902 for responding tospeech input, according to various examples. Process 902 is performed,for example, using devices 800 and/or 900, or using any componentthereof. In some examples, process 902 is performed using aclient-server system (e.g., 100) and the blocks of the process aredivided up in any manner between the server (e.g., DA server 106) andone or more client devices (e.g., 800 and 900). Thus, while portions ofprocess 902 are described herein as being performed by particulardevices of a client-server system, it will be appreciated that theprocess is not so limited. In process 902, some blocks are, optionally,combined, the order of some blocks is, optionally, changed, and someblocks are, optionally, omitted. In some examples, additional steps maybe performed in combination with process 902. For example, process 902can include the additional step of device 800 receiving, from one ormore external electronic devices, one or more speaker profiles for oneor more users, as discussed above. In some examples, the additional stepis performed before block 903, discussed below.

At block 903, device 800 receives a speech input.

At block 904, device 800 determines whether it has any registered users.As discussed, registered users are, for example, users having respectivespeaker profiles received by device 800. If device 800 does not have anyregistered users, device 800 provides a response to the speech input asdescribed above in FIGS. 7A-C. If device 800 has one or more registeredusers, process 902 proceeds to block 905.

At block 905, device 800 determines, based on the speech input, whetherto identify a user. In some examples, determining to identify a userincludes determining that a user intent associated with the speech inputincludes a personal intent or a semi-personal intent. In some examples,determining to identify a user includes determining that the speechinput includes one or more words indicative of personalization (e.g.,using module 730 and/or 732). Exemplary words indicative ofpersonalization include “my,” “mine,” “personal,” “my own,” “I,” and thelike. In some examples, determining not to identify a user includesdetermining that a user intent associated with the speech input includesa non-personal intent.

If device 800 determines not to identify a user, device 800 provides anon-personalized response to the speech input, as shown in block 953. Anon-personalized response may be a response not determined based on thepersonal information of any user. For example, in FIG. 10D, a user asksdevice 800 “what's the weather today?”. Device 800 determines based onthe speech input not to identify a user and provides a non-personalizedresponse to the speech input, “it's 70 degrees and sunny.”

If device 800 determines to identify a user, process 902 proceeds toblock 906. At block 906, device 800 determines whether the speech inputincludes a reference, such as a third-person reference, to an entity(e.g., using module 730 and/or 732). In some examples, a reference to anentity includes a name, such as a name of a registered user. Forexample, Stephen may say “read Stephen's messages.” In some examples, areference to an entity includes word(s) other than the entity's namesuch as “my mom,” “my dad,” “my boss,” “his,” “her,” “their,” and thelike. In some examples, if the speech input includes a reference to anentity, process 902 proceeds to block 907. In some examples, if thespeech input does not include a reference to an entity, process 902proceeds to block 932.

At block 907, device 800 determines whether the speech input isassociated with a predetermined category of intent (e.g., using naturallanguage processing module 732). Exemplary predetermined categories ofintents include intents of locating electronic devices (e.g., “where isStephen's phone?”), getting directions to/from locations or findinglocations (e.g., “take me to my sister's house,” “where is Stephen'scar?”), and providing weather information (e.g., “what's the weather atmy mom's house?”). In some examples, if the speech input is associatedwith a predetermined category of intent, process 902 proceeds to block932.

In some examples, if the speech input is associated with thepredetermined category of intent, a digital assistant initiates acorresponding task based on the reference to an entity, e.g., if device800 determines that the speech input corresponds to a user. For example,a parameter of a task initiated by task flow processing module 736 isbased on the reference to the entity. For example, for the speech input“what's the weather at my mom's house?,” a digital assistant performsthe task of getting weather information, where the task has a parameterof (location=the identified user's mom's house).

In some examples, if the speech input is not associated with apredetermined category of intent, process 902 proceeds to block 908. Atblock 908, process 909 (a sub process of process 902) is performed.

Turning to FIGS. 9C-D (process 909), at block 910, device 800 determineswhether the speech input is associated with a personal domain. Forexample, using natural language processing module 732, device 800determines a domain associated with the speech input and determineswhether the domain is a personal domain or a non-personal domain. Insome examples, a personal domain is associated with personal intents(e.g., actionable intents), as discussed above. Example personal domainsinclude a messages domain (e.g., associated with intents of retrieving auser's message information), a phone domain (e.g., associated withintents of calling/messaging a user's contacts), a notes domain (e.g.,associated with intents of retrieving/modifying a user's notes), areminder domain, a calendar domain, a health domain (e.g., associatedwith intents of retrieving/modifying a user's health data), and a devicelocation domain (e.g., associated with intents of locating a user'selectronic devices). In some examples, a non-personal domain isassociated with non-personal intents (e.g., actionable intents). Examplenon-personal domains include a media domain (e.g., associated withintents of providing/modifying media content) and a sports domain (e.g.,associated with intents of providing sports information). In someexamples, if the domain is a non-personal domain, device 800 provides aresponse to the speech input based on the determined domain, e.g., asdiscussed with respect to FIGS. 7A-C. In some examples, if the domain isa personal domain, process 909 proceeds to block 911.

At block 911, device 800 determines whether there is only one registereduser (e.g., only has received a speaker profile for one user). In someexamples, if there is only one registered user, process 909 proceeds toblock 912. In some examples, if there is not only one registered user,process 909 proceeds to block 913.

At block 912, device 800 determines whether the speech input correspondsto the only one user. For example, according to the above discussedtechniques, device 800 determines a degree of confidence (e.g., high,medium, low) that the speech input corresponds to the only one user. Insome examples, if the degree of confidence is high or medium, device 800determines that the speech input corresponds to the only one user. Insome examples, if the degree of confidence is low, device 800 determinesthat the speech input does not correspond to the only one user. In someexamples, if device 800 determines that the speech input corresponds tothe only one user, device 800 provides a response to the speech input.For example, suppose Stephen is the only registered user of device 800and says “read Stephen's messages” to device 800. Device 800 determineshigh confidence that the speech corresponds to Stephen and thus providesStephen's messages.

If device 800 determines that the speech input does not correspond tothe only one user, device 800 provides a response indicative of an error(e.g., audio output, displayed output). For example, device 800 providesa response indicative of user non-recognition (e.g., “I'm not sure whoyou are,” “Sony I can't do that”). In this manner, if Stephen is theonly registered user, and a non-registered user says “read Stephen'smessages” to device 800, device 800 does not undesirably provideStephen's messages.

Turning to block 913, device 800 determines whether the reference to theentity included in the speech input matches a name of any registereduser (e.g., using module 730 and/or 732). If the reference matches aname of a registered user, process 909 proceeds to block 914. If thereference does not match a name of a registered user, process 909proceeds to block 916.

At block 914, device 800 determines a confidence that the speech inputcorresponds to the registered user that matches the reference to theentity. For example, according to the above discussed techniques, device800 determines a degree of confidence that the speech input correspondsto the registered user. If the confidence is high, device 800 provides aresponse to the speech input, as shown by block 952. For example, inFIG. 10E, Stephen says “this is Stephen, read my messages” to device800. Device 800 determines a high confidence that the speech inputcorresponds to Stephen, and thus provides Stephen's messages.

If the confidence is medium or low, process 909 proceeds to block 915.At block 915, device 800 requests a user to confirm his or her identity,and determines whether a response to the request corresponds to theuser. In some examples, if device 800 determines that the responsecorresponds to the user (e.g., confirms the user), device 800 provides aresponse to the speech input. For example, if Stephen responds “Yes” todevice 800's request “are you Stephen?”, device 800 provides a responsepersonalized for Stephen, such as providing Stephen's messages. In someexamples, if device 800 determines that the response does not correspondto the user (e.g., does not confirm the user), device 800 provides aresponse indicative of an error (e.g., “Sorry I can't do that”).

At block 916, process 917 (a sub process of process 902) is performed.Turning to FIG. 9E (process 917), at block 918, device 800 determineswhether a previous input (e.g., previous to the speech input at block903) is associated with an identity domain. In some examples, theprevious input is the second most recent user input, with the speechinput in block 903 being the most recent. An identity domain isassociated with actionable intents of identifying a user and/or askingfor a user's identity, for instance. For example, an input of “who amI?” and an input of “I am [name]” (e.g., provided responsive to device800 outputting “please tell me who you are”) are each associated with anidentity domain.

In some examples, if the previous input is associated with an identitydomain, process 917 returns an indication to confirm a user. In someexamples, if process 917 returns an indication to confirm a user, device800 then requests a user to confirm his or her identity (e.g., asks “areyou [name]?”), as discussed above. In some examples, the name isdetermined based on the previous input, as device 800 knows the user'sname because the device recently identified the user based on theprevious input. In some examples, if a user confirms his or heridentity, device 800 determines the user's identity (e.g., name). Forexample, if Jessica previously said “I am Jessica” to device 800, thedevice can ask “this is Jessica right?” (instead of “who is this?”)responsive to a current speech input. If Jessica replies “yes,” device800 determines Jessica's identity. In this manner, device 800 may notundesirably ask for the user's identity again, as the user may have justidentified him/herself.

If the previous input is not associated with an identity domain, process917 proceeds to block 919. At block 919, device 800 determines whetherthe previous input includes an identity correction. For example, device800 determines whether the previous input is associated with a userintent of correcting a user's identity. For example, suppose in aprevious user-device interaction, device 800 incorrectly identifiedJessica, e.g., responded “ok Stephen reading your messages” to Jessica'sspeech input “read my messages.” Jessica may thus provide the input “noI'm Jessica.”

If the previous input includes an identity correction, process 917returns an indication to confirm a user, as discussed above.

If the previous input does not include an identity correction, process917 proceeds to block 920. At block 920, device 800 provides an outputrequesting a user to identify him/herself, e.g., “could you please tellme who you are?”. At block 920, device 800 further receives a speechinput responsive to the output (e.g., “I am Jessica”) and determineswhether the speech input includes a name, as discussed above. If thespeech input does not include a name (or otherwise does not indicate auser's identity), device 800 provides a response to the speech input.For example, if device 800 asks “please tell me who you are” and a usersays “never mind,” device 800 can output “okay” and cease responding tothe user.

If the speech input includes a name, process 917 proceeds to block 921.At block 921, device 800 determines whether the name matches a name of aregistered user. If the name matches the name of a registered user,process 917 returns an identification of the registered user. Forexample, if Jessica says “I am Jessica,” and Jessica is a registereduser, process 917 returns an identification of Jessica.

If the name does not match the name of a registered user, process 917proceeds to block 922. At block 922, device 800 determines whether thespeech input (received at block 903) is associated with a personaldomain, as discussed above. In some examples, if the request is notassociated with a personal domain, process 917 returns an identificationof the name (e.g., the name not matching the name of the registereduser) and an indication that the speech input is not associated with apersonal domain.

If the speech input is associated with a personal domain, device 800provides a response indicative of user non-recognition (e.g., “Sorry,I'm not sure who you are”).

Returning to FIGS. 9C-D (process 909), if block 916 returns anindication to confirm a user, process 917 repeats without performingblocks 918, 919, and/or 920. For example, process 917 proceeds directlyto block 921, where device 800 determines whether a confirmed name(e.g., Jessica confirmed her name by replying “yes” to device 800 asking“this is Jessica right?”) matches a name of a registered user.

If block 916 returns an identification of a registered user, process 909proceeds to block 923. At block 923, device 800 determines whether theidentification of the registered user matches the reference to theentity included in the speech input (e.g., received at block 903). Ifthe obtained identification of the registered user does not match thereference, process 909 returns an indication that user identificationbased on the speech input is required and that a digital assistantshould initiate a task based on the reference.

As an example of process 902 thus far, suppose Jessica asks “readNancy's messages,” where Nancy is not a registered user of device 800.Device 800 thus asks “could you please tell me who you are?”, to whichJessica responds “I am Jessica” (e.g., process 917). Device 800determines that “Jessica” does not match “Nancy.” For example, Jessicais requesting her messages from Nancy. Device 800 thus determineswhether the speech input “read Nancy's messages” corresponds to Jessica,and if so, initiates a task of providing Jessica's messages from Nancy.

If the obtained identification of the registered user matches thereference to the entity, process 909 proceeds to block 924. At block924, device 800 determines a degree of confidence that the speech inputreceived at block 920 (e.g., “I am [name]”) corresponds to the referenceto the entity included in the speech input received at block 903.

If the degree of confidence is medium or high, device 800 provides aresponse to the speech input received at block 903.

If the degree of confidence is low, process 909 proceeds to block 925.At block 925, device 800 determines whether the user whose name includedin the speech input received at block 920 has recently confirmed his/heridentity using his/her external electronic device, as discussed above.For example, device 800 determines whether the user has confirmedhis/her identity within a predetermined duration (e.g., 5, 10, 15, 30,60 seconds, 2 minutes, 5 minutes) before the speech input received atblock 920 or block 903.

If the user has not recently confirmed his/her identity using his/herexternal electronic device, process 909 returns an indication that userconfirmation is required. As discussed below with respect to FIG. 9F, ifuser confirmation is required, device 800 may attempt to confirm theuser's identity using the user's external electronic device. Forexample, suppose that Jessica says “read Harry's messages” to device800, where Harry is not a registered user of device 800. Device 800 thusasks “could you please tell me who you are?”, to which Jessica responds“I am Harry.” For example, Jessica is impermissibly trying to accessHarry's messages, not trying to access her own messages from Harry.Device 800 determines a low confidence that the speech input “I amHarry” corresponds to Harry and further determines that Harry has notrecently confirmed his identity using his external device. Device 800may thus cause Harry's external device to ask “read your messages?”, towhich Harry can respond “no.” In this manner, a user (e.g., Jessica) maynot undesirably access another user's personal information (e.g.,Harry's messages).

If the user has recently confirmed his/her identity using his/herexternal electronic device, device 800 provides a response to the speechinput received at block 903.

Returning to FIGS. 9A-B (process 902), if process 909 returns anindication that user identification based on the speech input isrequired, process 902 proceeds to block 932, discussed below.

If process 909 returns an indication that user confirmation is required,process 902 proceeds to block 926. At block 926, process 927 (a subprocess of process 902) is performed.

Turning now to FIG. 9F (process 927), at block 928, device 800determines a degree of confidence that a speech input corresponds to aname (e.g., a user having the name). In some examples, the speech inputis the speech input received at block 903. In some examples, the speechinput is a speech input provided responsive to a request for useridentity (e.g., at block 920). In some examples, device 800 determinesthe name based on the speech input responsive to the output indicativeof a request for user identity received at block 920, e.g., “I am[name].”

If the degree of confidence that the speech input corresponds to thename is medium or high, device 800 provides a response to the speechinput received at block 903.

If the degree of confidence that the speech input corresponds to thename is low, process 927 proceeds to block 929. At block 929, device 800determines a domain associated with the speech input received at block903. In some examples, if the domain is a domain of a first type, suchas a device location domain, device 800 provides a response indicativeof an error. For example, device 800 provides a response indicative ofuser non-recognition such as, “I'm sorry that doesn't sound like you.”In some examples, if the domain is a domain of a second type, such as adomain associated with actionable intents of providing media content,device 800 provides a response to the speech input received at block 903(e.g., provides media content). In some examples, if the domain is adomain of a third type, such as a personal domain, process 927 proceedsto block 930.

At block 930, device 800 causes an external electronic device to providea confirmation request, as discussed above. In some examples, theexternal electronic device is the device associated with the name inblock 928, e.g., associated with the user having the name.

At block 931, device 800 determines whether a user has confirmed theconfirmation request. For example, device 800 determines whether it hasreceived an indication of user confirmation of the confirmation request.If the user has confirmed the confirmation request, a response to thespeech input received at block 903 is provided, as shown in block 950.In some examples, device 800 provides the response. In some examples,the external electronic device provides the response. For example,suppose Jessica says “read my messages” to device 800 and then confirmsthe confirmation request “read your messages?” on her phone. Device 800and/or Jessica's phone may then provide Jessica's messages.

If the user has not confirmed the confirmation request (e.g., responds“no” to the confirmation request or otherwise dismisses the request),process 927 (and 902) ends. For example, device 800 does not provide anyfurther response to the speech input received at block 903.

Returning to FIGS. 9A-B, at block 932, device 800 identifies one or moreusers corresponding to the speech input received at block 903. Forexample, device 800 determines respective likelihoods that the speechinput corresponds to each registered user and/or a likelihood that thespeech input corresponds to a non-registered user. In some examples, atblock 932, device 800 further determines based on the determinedlikelihoods, a degree of confidence that the speech input corresponds toeach user of the registered users and/or a degree of confidence that thespeech input corresponds to a non-registered user. In some examples, atblock 932, device 800 determines a number of possible userscorresponding to the speech input.

In some examples, device 800 determines that there are more than twopossible users. For example, device 800 determines that it has at leasthigh or medium confidence that the speech input corresponds to each ofthe more than two users and/or that the more than two users cannot bedistinguished from each other.

In some examples, device 800 determines that there are two (e.g.,exactly two) possible users. For example, device 800 determines that ithas at least high or medium confidence that the speech input correspondsto each of the two users and/or that the two users cannot bedistinguished from each other.

In some examples, device 800 determines that there is one (e.g., exactlyone) possible user. For example, device 800 determines that (1) it hasthe highest confidence that the speech input corresponds to the oneuser, (2) it has at least medium or high confidence that the speechinput corresponds to the one user, and/or (3) the one user can bedistinguished from other users. As another example, device 800determines that the one user is the only user for which a likelihood isdetermined.

In some examples, device 800 determines that there are no possible users(e.g., that the speech input does not correspond to any user). Forexample, device 800 determines that it has low confidence that thespeech input corresponds to any user of the registered users.

If device 800 determines that there are more than two possible users,process 902 proceeds to block 933. At block 933, process 917 isperformed, as discussed above. If process 917 returns an indication toconfirm a user, process 902 proceeds to block 939, discussed below. Ifprocess 917 returns an identification of a name and an indication thatthe speech input is not associated with a personal domain, device 800provides a response to the speech input.

If process 917 returns an obtained identification of a registered user,process 902 proceeds to block 934 (process 927, discussed above). Forexample, suppose Stephen says “Hey Siri, read my messages” to device800. Device 800 determines that more than two possible users correspondto the speech input. Device 800 then asks “could you please tell me whoyou are?”, to which Stephen responds “I am Stephen.” Device 800determines a high confidence that “I am Stephen” corresponds to Stephen(block 928) and thus provides Stephen's messages.

If device 800 determines that there are no possible users, process 902proceeds to block 935. At block 935, device 800 determines whether thespeech input received at block 903 is associated with a personal domain.If the speech input is associated with a personal domain, device 800provides an output indicative of user non-recognition, as shown in block951. For example, in FIG. 10F, a non-registered user says “read mymessages” to device 800. Device 800 responds “I'm not sure who you are,you'll have to do that on your phone.”

If the speech input is not associated with a personal domain, process902 proceeds to block 936 (process 917, discussed above). If block 936returns an indication to confirm a user, process 902 proceeds to block939, discussed below. If block 936 returns an identification of a nameand an indication that the speech input is not associated with apersonal domain, device 800 provides a response to the speech input.

If block 936 returns an obtained identification of a registered user,process 902 proceeds to block 937 (process 927, discussed above).

If device 800 determines that there is one possible user, process 902proceeds to block 938. At block 938, device 800 determines whether adegree of confidence that the speech input received at block 903corresponds to the one user is high, medium, or low.

If the confidence that the speech input corresponds to the one user ishigh, device 800 provides a response to the speech input, as shown inblock 949. For example, suppose Jessica says “remind me to pick upgroceries tomorrow” and device 800 determines that Jessica is the onlypossible user and has high confidence that the speech input correspondsto Jessica. Device 800 thus creates a reminder entry of “pick upgroceries tomorrow” in Jessica's reminders and outputs “ok Jessica, I'llremind you.”

If the confidence that the speech input corresponds to the one user ismedium, process 902 proceeds to block 939. At block 939, device 800requests a user to confirm his or her identity. For example, device 800asks “are you [name]?”, where [name] is the name of the one user. Atblock 939, device 800 further determines whether a response to therequest corresponds to the user (e.g., confirms the user). For examples,device 800 determines whether the response includes an affirmative ornegative response.

If the device confirms the user, device 800 provides a response to thespeech input received at block 903. For example, suppose Jessica says“remind me to pick up groceries tomorrow” and device 800 determines thatJessica is the only possible user and has medium confidence that thespeech input corresponds to Jessica. Device 800 then asks “you areJessica right?”, to which Jessica replies “yes.” Device 800 thus createsa reminder entry of “pick up groceries tomorrow” in Jessica's remindersand outputs “ok Jessica, I'll remind you.”

If the user does not confirm his or her name, process 902 proceeds toblock 940 (process 917, discussed above). In some examples, if the userdoes not confirm his or her name, device 800 provides an outputindicative of an apology (e.g., “Sony I must have misidentified you”).

If block 940 returns an indication to confirm a user, block 940 repeatswithout performing blocks 918, 919, and/or 920. For example, asdiscussed above, device 800 determines whether the name corresponding toa request for a user to confirm his/her name in process 917 matches thename of a registered user (block 921). For example, suppose Jessica says“read my voice mails” to device 800. Device 800 (incorrectly) determinesthat Stephen is the only possible user corresponding to the speech inputand has medium confidence that the speech input corresponds to Stephen.Device 800 then asks “you are Stephen right?”, to which Jessica replies“no.” Device 800 then determines that Jessica previously told device 800that she was Jessica and thus asks “you are Jessica right?” (e.g.,process 917 returns an indication to confirm a user). Jessica replies“yes” and device 800 then determines whether Jessica is the name of aregistered user (block 921).

If block 940 returns an identification of a name and an indication thatthe speech input is not associated with a personal domain, device 800provides a response to the speech input received at block 903. Forexample, suppose a non-registered user Joe says “play my music” todevice 800. Device 800 (incorrectly) determines that Stephen is the onlypossible user corresponding to the speech input and has mediumconfidence that the speech input corresponds to Stephen. Device 800 thenasks “you are Stephen right?”, to which Joe replies “no.” Device 800then asks “please tell me who you are,” to which Joe replies “I am Joe.”Device 800 determines that Joe is not a registered user and that thespeech input “play my music” is not associated with a personal domain.Device 800 thus plays music (e.g., music from a default accountassociated with the device, discussed below).

If block 940 returns an obtained identification of a registered user,process 902 proceeds to block 941 (process 927), discussed above. Forexample, suppose Jessica says “read my voice mails” to device 800.Device 800 (incorrectly) determines that Stephen is the only possibleuser corresponding to the speech input and has medium confidence thatthe speech input corresponds to Stephen. Device 800 then asks “you areStephen right?”, to which Jessica replies “no.” Device 800 then asks“could you please tell me who you are?”, to which Jessica replies “I amJessica.” Device 800 determines high confidence that the speech input “Iam Jessica” corresponds to Jessica. Device 800 thus provides Jessica'svoicemails.

If the confidence that the speech input corresponds to the one user islow, process 902 proceeds to block 942. At block 942, device 800determines whether the one user has recently confirmed his/her identityusing his/her external electronic device. For example, device 800determines whether the one user has recently confirmed his/her identityusing his/her external electronic device within a predetermined duration(e.g., 5, 10, 15, 30, 60 seconds, 2 minutes, 5 minutes) before thespeech input received at block 903. If the one user has recentlyconfirmed his/her identity, device 800 provides a response to the speechinput. For example, suppose Jessica asks device 800 “what is my creditcard balance?”. Device 800 determines that Jessica is the only possibleuser, but has low confidence that the speech input corresponds toJessica. However, device 800 determines that Jessica has recentlyconfirmed her identity using her external electronic device. Device 800thus provides the response “your credit card balance is $200,” forexample.

If the one user has not recently confirmed his or her identity, process902 proceeds to block 933, discussed above.

If device 800 determines that there are two possible users, process 902proceeds to block 943. At block 943, device 800 determines whether thereare more than two registered users. If there are more than tworegistered users, process 902 proceeds to block 933.

If there are not more than two registered users, process 902 proceeds toblock 944. At block 944, device 800 determines whether a non-registereduser is a user of the two possible users.

If device 800 determines that a non-registered user is a user of the twopossible users, process 902 proceeds to block 945 (process 917). Ifblock 945 returns an indication to confirm a user, process 902 proceedsto block 939. If block 945 returns an identification of a name and anindication that the speech input is not associated with a personaldomain, device 800 provides a response to the speech input. If block 945returns an obtained identification of a registered user, process 902proceeds to block 946 (process 927).

If device 800 determines that a non-registered user is not a user of thetwo possible users, in some examples, process 902 proceeds to block 947.In other examples, process 902 proceeds to block 945.

At block 947, device 800 provides an output requesting userdisambiguation between the two possible users and receives a response tothe output. In some examples, the output includes the name of the twopossible users. At block 947, device 800 further determines whether theresponse disambiguates between the two possible users. For example aresponse including “[name],” where [name] is the name of one of the twopossible users, disambiguates between the two possible users.

If the response does not disambiguate between the two possible users,process 902 proceeds to block 933. For example, process 902 proceeds toblock 933 when “[name]” is not the name of one of the two possibleusers, or the response does not otherwise disambiguate between theusers. For example, suppose Corey asks device 800 “find my phone.”Device 800 incorrectly determines that Jessica and Stephen are twopossible users corresponding to the speech input. Device 800 thus asks“whose phone, Jessica's or Stephen's,” to which Corey replies “neither.”Device 800 may thus ask “could you please tell me who you are?” (block920 in process 917).

If the response does disambiguate between the two possible users,process 902 proceeds to block 948 (process 927, discussed above). Forexample, suppose Stephen asks device 800 “find my phone.” Device 800determines that Stephen and Jessica are two possible users correspondingto the speech input. Device 800 thus asks “whose phone, Stephen's orJessica's?”, to which Stephen responds “Stephen.” Device 800 may thusprovide the location of Stephen's phone, e.g., output “Stephen, yourphone is at your office.”

5. Providing Personalized Media Content

FIGS. 11A-B illustrate a flowchart of process 1100 for providing mediacontent, according to some examples. Process 1100 is performed, forexample, using devices 800 and/or 900, or using any component thereof.In some examples, process 1100 is performed using a client-server system(e.g., 100) and the blocks of the process are divided up in any mannerbetween the server (e.g., DA server 106) and one or more client devices(e.g., 800 and 900). Thus, while portions of process 1100 are describedherein as being performed by particular devices of a client-serversystem, it will be appreciated that the process is not so limited. Inprocess 1100, some blocks are, optionally, combined, the order of someblocks is, optionally, changed, and some blocks are, optionally,omitted. In some examples, additional steps may be performed incombination with process 1100.

At block 1102, device 800 receives a spoken request. In some examples, aspoken request includes a spoken media request for media content, suchas songs, albums, artists, videos, books, news, podcasts, playlists,radio stations, and the like. Exemplary requests for media contentinclude “play my music,” “play Shake it off by Taylor Swift,” “play theworkout playlist,” “what's the news?,” “play sad music,” “play Jessica'smusic,” “play This American Life,” “switch to NBC news,” “play myfavorite radio station,” and the like. In some examples, a spoken mediarequest includes a request to modify a user's media content, such as topurchase media content, add/remove media content to/from a mediacollection (e.g., playlist), switch a content provider (e.g., newsprovider), subscribe to a content provider, like or dislike mediacontent, or otherwise modify media content associated with a user.

In some examples, a spoken media request includes a name of a user(e.g., registered user). In some examples, the name is different fromthe name of the user who provided the spoken media request. For example,Stephen in FIG. 8 may say “play Jessica's music.” In this manner, a userof device 800 may request media content associated with other registeredusers of the device.

In some examples, a spoken media request includes a name of a mediacollection. In some examples, the media collection is associated with auser different from the user who provided the spoken media request. Forexample, if Jessica (a registered user) has a playlist titled “workout”and Stephen does not, Stephen may say “play the workout playlist.” Inthis manner, a user of device 800 may request media collectionsassociated with other users.

At block 1104, device 800 determines whether the spoken request includesa media request. For example, device 800 determines using module 732whether the spoken request corresponds to a media domain, e.g., a domainassociated with the actionable intents of providing and/or modifyingmedia content. If device 800 determines that the spoken request includesa media request (e.g., corresponds to a media domain), process 1100proceeds to block 1106. If device 800 determines that the spoken requestdoes not include a media request (e.g., does not correspond to a mediadomain), the spoken request is processed as discussed above with respectto FIGS. 9A-F.

At block 1106, device 800 determines a number of possible userscorresponding to the spoken request according to the techniquesdiscussed above. For example, device 800 determines whether a user, of aplurality of registered users, corresponds to the spoken request. Insome examples, device 800 determines that a first user (e.g., exactlyone user) of the plurality of registered users corresponds to the spokenrequest. For example, device 800 determines that it is highly confidentthe spoken request corresponds to the first user, has distinguished thefirst user from other registered users, and is most confident that thespoken request corresponds to the first user. In accordance withdetermining that the first user corresponds to the spoken request,process 1100 proceeds to block 1108.

At block 1108, device 800 provides a response to the spoken request. Insome examples, the response is personalized for the identified user(first user). In some examples, the response to the spoken requestincludes one or more words indicative of personalization for theidentified user. For example, the response includes a name of theidentified user and/or words such as “just for you,” “your,” “yourpersonal,” and the like.

In some examples, a response to a spoken request includes playback of amedia item from a media account associated with a user (e.g., personalmedia account). A media account associated with a user includes mediacontent belonging to that user. In some examples, the media account isassociated with the identified user. For example, as shown in FIG. 10G,Jessica says “play Perfect by Ed Sheeran” and device 800 identifiesJessica. Device 800 thus plays a version of the song “Perfect” includedin Jessica's personal media account, the live version.

In some examples, providing a response to a spoken request includesupdating a media account. In some examples, the media account isassociated with the identified user. In some examples, updating a mediaaccount includes modifying a user's media content, as discussed above.For example, if Jessica says “add Shake it off to my workout playlist,”device 800 adds the song to Jessica's workout playlist. As anotherexample, if Jessica says “subscribe to This American Life,” device 800updates Jessica's personal media account to subscribe to the podcast“This American Life.”

In some examples, updating a media account includes updating a mediapreference (e.g., of the identified user) based on the spoken request. Amedia preference indicates various user-specific media preferences suchas liked/disliked media content, liked/disliked media genres, playcounts for media content, skipped media content, and the like, forinstance. A user's media preference can be used to provide mediapreferred by the user (e.g., when the user is identified). For example,if Jessica says “play Shake it off by Taylor Swift,” device 800 canincrement Jessica's play count for the song “Shake it off,” updateJessica's media preference to indicate a preference for pop music,and/or update the media preference to indicate a preference for TaylorSwift. Thus, the next time Jessica requests media content, device 800can provide media content based on Jessica's updated preferences (e.g.,bias media content towards pop music).

In some examples, updating a media preference includes updating acontent provider preference based on the spoken request. A contentprovider preference indicates a content provider (e.g., news source,website) preferred by a user. For example, while device 800 providesmedia content from a first content provider (e.g., Fox News), Jessicarequests to switch to a second content provider (e.g., says “switch toCNN”). Device 800 then indicates that the content provider has beenswitched (e.g., outputs “ok here's some news from CNN” and/or providesnews from CNN). In some examples, device 800 further updates Jessica'scontent provider preference to be the second content provider. In thismanner, when Jessica subsequently requests the news, device 800 providesthe news from the updated content provider (e.g., CNN).

In some examples, a response to a spoken request includes playback of amedia item associated with a user different from the user who providedthe spoken request. In some examples, device 800 obtains the media itemfrom a media account associated with the different user. For example, ifStephen says “play Jessica's music,” and device 800 identifies Stephen,device 800 obtains and provides media content from Jessica's mediaaccount.

In some examples, a response to a spoken request includes playback of amedia item from a media collection associated with a user different fromthe user who provided the spoken request. In some examples, device 800obtains the media item from the media collection associated with thedifferent user. For example, if Stephen says “play the workoutplaylist,” and Jessica is the only registered user with a playlisttitled “workout,” device 800 plays media content from Jessica's“workout” playlist.

As discussed, the present disclosure contemplates allowing a user toaccess media content associated with other users. Thus, it may bedesirable for device 800 to select a correct media account (associatedwith a correct user) from which to provide media content. Exampletechniques for selecting a media account are now discussed.

In some examples, selecting a media account includes determining whetherrequested media content matches media content in a media account ormedia database. For example, using the STT processing techniquesdiscussed with respect to FIGS. 7A-C, device 800 determines a scoreindicating a degree to which a spoken request (or portion thereof)matches media content in a media account. If the score is high (e.g.,greater than a threshold), device 800 determines that the requestedmedia is in the media account and/or provides the best matching mediacontent from the media account. If the score is low (e.g., less than athreshold), device 800 determines that the requested media is not in themedia account and/or does not provide media content from the mediaaccount. In some examples, words representing the media content (e.g.,song names, artist names, playlist names, subscribed podcast names, newsprovider names, and the like) of media accounts associated withregistered users are included in vocabulary 744. In some examples, STTprocessing module 730 uses the vocabulary to determine the score, asdiscussed with respect to FIGS. 7A-C.

In some examples, device 800 first determines whether requested mediacontent matches media content in the identified user's media account(personal media account). For example, device 800 determines a score asdiscussed above. In some examples, if the score is high, device 800determines that the requested media content is in the identified user'smedia account and provides the requested media content from the account.In some examples, if the score is low, device 800 determines that therequested media content is not in the identified user's media accountand does not provide the requested media content from the account. Forexample, the score determined for Jessica's spoken request “play Shakeit off by Taylor Swift” may be high because Jessica's personal mediaaccount includes the song “Shake it off” by Taylor Swift.

In some examples, device 800 determines whether requested media contentmatches media content in a media database not associated with anyparticular user. In some examples, a media database includes a largeamount of media content available through a media provider such as AppleMusic by Apple Inc., Spotify®, SoundCloud, and the like. In contrast, amedia account associated with a particular user includes a limitedamount of media content, such as media content selected by the user, forinstance. In some examples, device 800 determines whether requestedmedia content matches content in a media database (e.g., by determininga score as discussed) in accordance with determining that the requestedmedia content is not in the identified user's account. In this manner,device 800 may first determine whether an identified user's personalmedia account includes requested content, and if not, then determinewhether a larger media database includes such content. For example, ifJessica says “play Hello by Adele,” and Jessica's personal account doesnot include the song “Hello,” device 800 can provide (e.g., stream) thesong from a media database.

In some examples, device 800 determines whether requested media contentmatches media content in a default media account associated with device800. In some examples, a default media account is a media accountassociated with a registered user of device 800 and is user designatedduring a set-up process for device 800. In some examples, a defaultaccount is subscribed to a media provider so that media content providedby the media provider is available to (e.g., included in) the defaultaccount. In some examples, device 800 determines whether requested mediacontent matches media content in the default media account in accordancewith determining that the requested media content is not in theidentified user's media account and/or not in a media database. Forexample, device 800 determines media content in the default account thatbest matches the requested media content and provides the best matchingmedia content.

In some examples, device 800 determines whether requested media contentmatches media content in a media account other than the identifieduser's media account (other media account). In some examples, the othermedia account is a personal media account associated with anotherregistered user of device 800. In some examples, device 800 determineswhether requested media content is in another media account inaccordance with determining that the requested media content is not inthe identified user's media account and/or not in a media database. Forexample, if Jessica requests an album not in her media account and notin a media database, but another registered user's account includes thealbum, device 800 can provide the album.

In some examples, a spoken request includes a name of a user (e.g.,“play Stephen's workout playlist”). In some examples, in accordance withdetermining that a spoken request includes a name of a user, device 800determines whether requested media content matches media content in amedia account associated with that user. In this manner, users mayrequest media content from both their own media accounts and from mediaaccounts of other registered users. For example, if Jessica says “playStephen's workout playlist,” device 800 can provide media content fromStephen's workout playlist.

Returning to block 1106, in some examples, device 800 determines that nouser of the plurality of registered users corresponds to the spokenrequest. For example, according to the above discussed techniques,device 800 determines a low confidence that any user of the registeredusers corresponds to the spoken request. In some examples, in accordancewith determining that no user of the plurality of registered userscorresponds to the spoken request, device 800 forgoes updating any mediapreference of any user based on the spoken request.

At block 1110, in accordance with determining that no user of theplurality of registered users corresponds to the spoken request, device800 determines whether the spoken request includes a personal request(e.g., personal media request). In some examples, a personal requestincludes a request for which device 800 should be highly confident thatthe request corresponds to a particular user to perform an associatedtask. Exemplary personal requests include “add this to my playlist,”“purchase this song,” “subscribe to this podcast,” “play my music,”“play my favorite playlist,” and the like. In some examples, determiningthat a spoken requests includes a personal request includes determiningthat the spoken request includes a request to modify a user's mediacontent. In some examples, determining that a spoken request includes apersonal request includes determining that the spoken request includesone or more words indicative of personalization. Exemplary wordsindicative of personalization include a registered user's name, pronounssuch as “me,” “my,” “mine,” “his,” “her,” and words such as “personal,”“personalized,” “just for me,” and “favorite.” In some examples,determining that a spoken request includes a personal request includesdetermining that the spoken request is associated with a predeterminedtype of user intent (e.g., personal intent, semi-personal intent), asdiscussed above.

At block 1112, in accordance with determining that the spoken requestincludes a personal request, device 800 obtains an identification of auser who provided the spoken request. For example, device 800 uses anyof the above discussed techniques (other than identifying the user basedon the spoken request) to obtain an identification of the user. Forexample, device 800 provides an output indicative of a request for useridentity, such as “who are you?”. In some examples, in response toproviding the output indicative of the request for user identity, device800 receives a speech input, such as “I am Jessica.” In some examples,device 800 obtains the identification of the user (e.g., Jessica) basedon the speech input according to the above discussed techniques.

In some examples, in accordance with obtaining the identification,device 800 provides a response to the spoken request, as shown in block1108. In some examples, the response is personalized for the identifieduser.

In some examples, device 800 is unable to obtain an identification of auser who provided the spoken user request. For example, a user may notrespond to device 800's output indicative of a request for user identitywithin a predetermined duration. In some examples, device 800 determinesthat the user who provided the spoken user request is not a registereduser. For example, a non-registered user Bob says “I am Bob” responsiveto device 800 outputting “who are you?”. In some examples, in accordancewith being unable to obtain an identification of a user and/ordetermining that the user is not a registered user, process 1100proceeds to block 1114.

At block 1114, device 800 determines whether the spoken request includesa request to provide media content (e.g., using module 732), such as toprovide a song, video, podcast, playlist, and the like. In someexamples, in accordance with determining that the spoken requestincludes a request to provide media content, process 1100 proceeds toblock 1116, discussed below. In some examples, in accordance withdetermining that the spoken request does not include a request toprovide media content, device 800 provides an output indicative of anerror, e.g., “sorry I can only do that for registered users.” Forexample, if device 800 determines that the spoken request includes arequest to modify a user's media content (not to provide media content),device 800 provides an output indicative of an error.

At block 1116, in accordance with determining that the spoken requestdoes not include a personal request, device 800 determines whether amedia account of a first type (e.g., default account) is associated withthe device. In some examples, in accordance with determining that amedia account of a first type is associated with the device, device 800provides a response to the spoken request, as shown in block 1118. Insome examples, the response is based on the media account of the firsttype. For example, device 800 provides the media content from a defaultaccount that best matches media content requested by the spoken request.For example, in FIG. 10H, a non-registered user says “Play Perfect by EdSheeran” (a non-personal request) to device 800. Device 800 thusprovides a version (e.g., studio version) of the song “Perfect” from adefault account associated with the device.

At block 1120, in accordance with determining that a media account ofthe first type is not associated with the electronic device, device 800provides a response to the spoken request. In some examples, theresponse is based on a media account of a second type different from thefirst type. In some examples, the second type of media account is afallback account different from a default account. In some examples, afallback account is selected by device 800 (or by a media provider) fromthe media accounts of the registered users and is the same account forevery spoken request. In some examples, a fallback account is subscribedto a media provider (e.g., Apple Music by Apple Inc.) so that mediacontent provided by the media provider is available to the fallbackaccount. For example, if device 800 is not associated with a defaultaccount, device 800 provides media content from a fallback account thatbest matches the spoken request.

In some examples, the spoken request requests media content not in adefault account. In such examples, device 800 provides media contentfrom a fallback account if media content in the fallback account matchesthe requested media content, e.g., even if the device has a defaultaccount. For example, if a user says “play Poker Face by Lady Gaga” anda default account associated with device 800 does not include the song,device 800 still provides the song from the fallback account.

In some examples, device 800 is not associated with a default account.In such examples, device 800 can provide media content from a fallbackaccount that best matches the spoken request (e.g., process 1100proceeds from block 1110 to block 1120 without performing blocks 1116 or1118). In some examples, device 800 provides media content from a mediaaccount associated with a most recently identified user, e.g., whendevice 800 determines that no registered user corresponds to the spokenrequest and that the spoken request does not include a personal request.In some examples, device 800 provides media content from a media accountassociated with a most frequently identified user, e.g., when device 800determines that no registered user corresponds to the spoken request andthat the spoken request does not include a personal request.

Returning to block 1106, in some examples, device 800 determines that aplurality of users (possible users) of the plurality of registered userscorrespond to the spoken request. For example, according to the abovediscussed techniques, device 800 determines high confidence that thespoken request corresponds to each of the possible users and/or that thepossible users cannot be distinguished from each other.

In some examples, at block 1122, in accordance with determining that aplurality of users correspond to the spoken request, device 800determines whether the spoken request includes a personal requestaccording to the above discussed techniques. In some examples, inaccordance with determining that the spoken media request does notinclude a personal request, process 1100 proceeds to block 1116,discussed above.

At block 1124, in accordance with determining that the spoken mediarequest includes a personal request, device 800 determines whether it isassociated with a media account of a first type (e.g., default account).In some examples, in accordance with determining that device 800 is notassociated with a media account of the first type, process 1100 proceedsto block 1112, discussed above.

At block 1126, in accordance with determining that device 800 isassociated with a media account of the first type, device 800 determineswhether a user associated with the media account of the first type is apossible user. In some examples, in accordance with determining that theuser associated with the media account of the first type is a possibleuser, device 800 provides a response to the spoken request, as shown inblock 1128. In some examples, the response to the spoken request isbased on the media account of the first type. For example, device 800provides, from the media account of the first type, media content bestmatching the spoken request. For example, suppose Jessica says “play mymusic” and device 800 cannot distinguish Jessica from other registeredusers. However, device 800 determines that Jessica is a possible usercorresponding to the spoken request. Thus, device 800 provides mediacontent from Jessica's personal media account.

In some examples, in accordance with determining that the userassociated with the media account is not a possible user, process 1100proceeds to block 1112, discussed above.

In some examples, device 800 is not associated with a media account ofthe first type. In such examples, device 800 may determine whether auser associated with a media account of a second type (e.g., fallbackaccount) is a possible user and/or provide a response to the spokenrequest based on the media account of the second type, analogous to theabove discussed techniques.

In some examples where device 800 is not associated with a media accountof the first type, in accordance with determining that the spokenrequest includes a personal request (block 1122), device 800 determineswhether a most recently identified user or a most frequently identifieduser is a possible user. In some examples, in accordance withdetermining that a most recently identified user is a possible user,device 800 provides a response to the spoken request based on a mediaaccount associated with the most recently identified user. In someexamples, in accordance with determining that a most frequentlyidentified user is a possible user, device 800 provides a response basedon a media account associated with the most frequently identified user.For example, suppose Jessica says “add this song to my workout playlist”and device 800 cannot distinguish Jessica from other registered users.However, device 800 determines that Jessica is a possible user and thatJessica is the most frequently identified user. Thus, device 800 adds acurrently playing song to Jessica's workout playlist.

6. Obtaining Information to Provide a Personalized Response

As discussed, one aspect of the present technology includes providingresponses personalized for an identified user. Exemplary techniques toobtain information to provide personalized responses (e.g., personalinformation) are now discussed.

FIG. 12 illustrates exemplary system 1200 for obtaining personalinformation. System 1200 includes device 800, external device 900, anddigital assistant server 1202. In some examples, system 1200 includesother external electronic devices (not shown) associated with otherusers, e.g., users other than the user associated with device 900. Theother external electronic devices may be similar to device 900. Forexample, the other external electronic devices are implemented as device400 or 600 and/or include the modules and functions of a digitalassistant.

In some examples, digital assistant server 1202 is implemented usingsystem 108 of FIG. 1 and devices 800 and 900 communicate with server1202, e.g., as shown in FIG. 1. In some examples, device 800 obtainspersonal information from server 1202, device 900, other externalelectronic devices, or a combination or sub-combination thereof,according to the techniques discussed below.

Each external electronic device stores personal information associatedwith a respective user. Exemplary personal information includes a user'scontacts information (e.g., contact names, addresses, phone numbers),communication data and/or metadata (e.g., text messages, emails, callhistory, voicemails, instant messages, message senders, message times),speaker profile and corresponding digital assistant identifier(discussed below), calendar and/or reminder information (e.g., calendaritems, reminder items), notes (e.g., user created text memos and/orvoice memos), media data (e.g., music, videos, photos, audiobooks, mediapreferences (e.g., favorite songs, liked songs, disliked songs,) mediaaccount data), health data (e.g., distance traveled, vitals data,calories burned), financial data (e.g., credit card balance, bankaccount balance, recent purchases), application data (e.g., internetsearch history, installed applications, social media data (e.g., posts,friend lists)), location data (e.g., a location of the external device,a user's frequently visited locations), data associated with a user'sresidence (e.g., number of locks, whether lights are on or off,thermostat settings), and voice shortcut data.

In some examples, an external electronic device sends certain personalinformation to server 1202 and/or to device 800. In some examples, theexternal electronic device sends such information only upon userapproval (e.g., through a user setting, through informed user consent).The personal information sent includes a speaker profile, informationassociated with contacts of a user (e.g., contact names), user calendarand/or reminder information (e.g., reminder list names), or acombination or sub-combination thereof, for instance.

In some examples, a speaker profile for a user corresponds to (e.g.,maps to) a digital assistant identifier. In some examples, theinformation sent to server 1202 further includes the digital assistantidentifier. A digital assistant identifier is associated with a user andidentifies an instance of a digital assistant associated with the user.For example, the digital assistant identifier “DA id #1” may identify aninstance of a digital assistant associated with a first user (e.g.,operating on the first user's device 900). In some examples, byidentifying a user using his or her speaker profile, a digital assistantidentifier associated with the user is determined (e.g., using themapping between the speaker profile and the digital assistantidentifier). Device 800 uses a digital assistant identifier to obtainpersonal information according to the techniques discussed below.

In some examples, device 800 obtains a digital assistant identifierassociated with a user. In some examples, obtaining a digital assistantidentifier includes receiving a speech input and identifying a useraccording to the techniques discussed herein. For example, device 800determines likelihoods that received speech input corresponds toregistered users and sends the likelihoods to server 1202. In someexamples, device 800 sends the received speech input to server 1202.Based on the received likelihoods and/or speech input, server 1202identifies a user according to the techniques discussed herein. In someexamples, server 1202 determines a digital assistant identifierassociated with the identified user (e.g., using a mapping between theidentified user's speaker profile and the digital assistant identifier)and sends the digital assistant identifier to device 800. For example,as shown in step 1210, device 800 obtains from server 1202 the digitalassistant identifier “DA id #1” associated with a first identified user.

In some examples, device 800 determines a digital assistant identifier(e.g., without using server 1202). For example, based on a receivedspeech input, device 800 identifies a user using his or her speakerprofile according to the techniques discussed herein. Device 800 thenuses a mapping between the identified user's speaker profile and adigital assistant identifier to determine the digital assistantidentifier associated with the identified user, for instance.

In some examples, device 800 determines or obtains a digital assistantidentifier associated with a user other than the identified user. Forexample, if the speech input includes a reference to a person (e.g.,“where is my mom's phone?”), device 800 determines or obtains a digitalassistant identifier associated with that person. For example, using STTprocessing module 730 and/or natural language processing module 732,server 1202 determines the person's name (and thus their speakerprofile) and determines the digital assistant identifier associated withthe person (e.g., a user's mom) based on a mapping between speakerprofiles and digital assistant identifiers. In some examples, server1202 then sends the digital assistant identifier to device 800.

In some examples, device 800 determines a communication identifiercorresponding to an obtained digital assistant identifier. Acommunication identifier identifies a particular electronic deviceoperating an instance of a digital assistant. In some examples, device800 stores a mapping of digital assistant identifiers to communicationidentifiers and uses such mapping to determine a communicationidentifier corresponding to an obtained digital assistant identifier.For example, device 800 obtains the digital assistant identifier “DA id#1” and determines the corresponding communication identifier “Com id#1” identifying device 900 (e.g., the first user's device). In thismanner, device 800 can map an obtained digital assistant identifierassociated with a user to a communication identifier identifying theuser's device.

In some examples, using a communication identifier, device 800establishes a communication session with a device identified by thecommunication identifier. For example, using the communicationidentifier “Com id #1,” device 800 establishes a communication sessionwith device 900, enabling exchange of data and/or commands between thedevices. In some examples, the data and/or commands are exchanged viaone or more of the communication protocols discussed above with respectto RF circuitry 208.

In some examples, in accordance with establishing a communicationsession, steps 1220 and 1230 are performed, as shown in FIG. 12. In someexamples, performing steps 1220 and 1230 enables device 800 to obtainpersonal information to provide responses personalized for a user.

At step 1220, device 800 sends a command to an external device (e.g.,900). In some examples, the command requests the external device toperform an action associated with a task determined based on receivedspeech input. For example, server 1202 and/or device 800 determines atask based on received speech input according to the techniquesdiscussed herein. In examples where server 1202 determines the task,server 1202 sends the determined task (e.g., executable instructions toperform the task) to device 800. In some examples, device 800 determinesa command based on a determined task and sends the command to theexternal device. For example, a task of obtaining Stephen's messages isdetermined from the speech input “Hey Sin, read my messages” and device800 determines a command requesting device 900 (e.g., Stephen's device)to provide Stephen's messages. As another example, a task of obtainingthe location of an external device associated with an identified user'smom is determined from the speech input “where is my mom's phone?” anddevice 800 determines a command requesting the external device toprovide its location.

In some examples, in accordance with receiving a command, the externaldevice performs an action requested by the command and provides resultsbased on the action to device 800. For example, at step 1230, theexternal device provides personal information to device 800. Device 800receives the personal information and uses the personal information toprovide responses personalized for an identified user as discussedherein. For example, in accordance with receiving the command requestingprovision of Stephen's messages, device 900 retrieves Stephen's messagesand provides the messages to device 800. Using the received messages,device 800 provides the response “Ok Stephen reading your messages:first message: Corey says meeting at 2'o clock,” e.g., as shown in FIG.8.

In some examples, device 800 receives personal information from server1202. As discussed, in some examples, server 1202 stores limited typesand/or amounts of personal information associated with users (e.g.,reminder list names), while much of users' personal information (e.g.,message contents) may be stored on the respective devices of the users(e.g., 900). Thus, in examples where personal information stored onserver 1202 can be used to provide a personalized response, server 1202sends personal information to device 800 (e.g., in addition to orwithout external device(s) sending personal information). For example,based on received speech input, server 1202 identifies a user anddetermines a task. Based on the identified user and the determined task,server 1202 determines the user's personal information appropriate forthe task and sends the personal information to device 800. For example,based on speech input “what's the name of my reminder list?” (e.g.,received by device 800), server 1202 identifies a user and determines atask of providing a name of the user's reminder list. Server 1202determines the name of the identified user's reminder list, and providesthe name to device 800.

7. Process for Responding to Speech Inputs

FIGS. 13A-G illustrate process 1300 for responding to speech inputs,according to various examples. Process 1300 is performed, for example,using one or more electronic devices implementing a digital assistant.In some examples, process 1300 is performed using a client-server system(e.g., system 100), and the blocks of process 1300 are divided up in anymanner between the server (e.g., DA server 106) and a client device. Inother examples, the blocks of process 1300 are divided up between theserver and multiple client devices (e.g., a mobile phone and a smartwatch). Thus, while portions of process 1300 are described herein asbeing performed by particular devices of a client-server system, it willbe appreciated that process 1300 is not so limited. In other examples,process 1300 is performed using only a client device (e.g., user device104) or only multiple client devices. In process 1300, some blocks are,optionally, combined, the order of some blocks is, optionally, changed,and some blocks are, optionally, omitted. In some examples, additionalsteps may be performed in combination with the process 1300.

At block 1302, a plurality of speaker profiles for a plurality of usersare received from one or more external electronic devices. In someexamples, the plurality of speaker profiles include a first speakerprofile for a first user, the first speaker profile including aplurality of representations of the voice of the first user and a secondspeaker profile for a second user, the second speaker profile includinga plurality of representations of the voice of the second user. In someexamples, at least one of the plurality of representations of the voiceof the first user is determined based on a first utterance of the firstuser, where the first utterance is received by a first externalelectronic device of the one or more external electronic devices, andwhere the first external electronic device is associated with the firstuser. In some examples, at least one of the plurality of representationsof the voice of the second user is determined based on a secondutterance of the second user, where the second utterance is received bya second external electronic device of the one or more externalelectronic devices, and where the second external electronic device isassociated with the second user.

At block 1304, a natural language speech input is received (e.g., block903).

At block 1306, a representation of the natural language speech input isdetermined, e.g., using a speaker model, according to some examples.

At block 1308, a first likelihood that the natural language speech inputcorresponds to the first user of the plurality of users and a secondlikelihood that the natural language speech input corresponds to thesecond user of the plurality of users are determined based on comparingthe natural language speech input to the plurality of speaker profiles(e.g., block 932). In some examples, the second likelihood is less thanthe first likelihood. In some examples, determining the first likelihoodincludes comparing the representation of the natural language speechinput to each of the plurality of representations of the voice of thefirst user, as shown in block 1310. In some examples, determining thesecond likelihood includes comparing the representation of the naturallanguage speech input to each of the plurality of representations of thevoice of the second user, as shown in block 1312.

At block 1314, it is determined whether the first likelihood and thesecond likelihood are within a first threshold (e.g., differencethreshold) (e.g., block 932).

At block 1316, it is determined whether the first likelihood is greaterthan a second threshold (e.g., an upper threshold) (e.g., block 938), insome examples.

At block 1318, in accordance with determining that the first likelihoodand the second likelihood are not within the first threshold, a responseto the natural language speech input is provided, the response beingpersonalized for the first user (e.g., block 949). In some examples,providing the response is performed further in accordance withdetermining that the first likelihood is greater than the secondthreshold. In some examples, the natural language speech input includesa request to provide a message associated with the first user andproviding the response to the natural language speech input includesproviding the message. In some examples, the natural language speechinput includes a request to provide media and providing the response tothe natural language speech input includes providing media associatedwith the first user. In some examples, the natural language speech inputincludes a request to communicate with a contact associated with thefirst user (e.g., “Call mom”) and providing the response to the naturallanguage speech input includes providing an output indicative of acommunication with the contact (e.g., “Calling mom”). In some examples,the response to the natural language speech input includes a fourth nameof the first user.

At block 1320, in some examples, in accordance with determining that thefirst likelihood and the second likelihood are within the threshold: anoutput indicative of a request for user identity is provided (e.g.,block 920, 930, 939, and/or 947).

At block 1322, in response to providing the output indicative of therequest for user identity, a third natural language speech input isreceived (e.g., block 920, 939, and/or 947), in some examples.

At block 1324, it is determined whether the third natural languagespeech input corresponds to the first user, in some examples. In someexamples, determining that the third natural language speech inputcorresponds to the first user includes determining that the thirdnatural language speech input includes a name of the first user, asshown in block 1326 (e.g., block 920 and/or 921). In some examples, theoutput indicative of the request for user identity includes a requestfor the first user to confirm their identity, the request including asecond name of the first user (e.g., block 939). In some examples,determining that the third natural language speech input corresponds tothe first user includes determining that the third natural languagespeech input includes an affirmative response (e.g., block 939), asshown in block 1328. In some examples, the output indicative of therequest for user identity includes a request for user disambiguationbetween the first user and the second user, the request including athird name of the first user and a name of the second user (e.g., block947). In some examples, determining that the third natural languagespeech input corresponds to the first user includes determining that thethird natural language speech input includes the third name of the firstuser (e.g., block 947), as shown in block 1330.

At block 1332, in accordance with determining that the third naturallanguage speech input corresponds to the first user, the response to thenatural language speech input is provided, in some examples.

At block 1334, in some examples, in accordance with determining that thefirst likelihood and the second likelihood are within the threshold, athird external electronic device of the plurality of external electronicdevices is caused to provide a confirmation request, the third externalelectronic device being associated with the first user (e.g., block930).

At block 1336, in some examples, an indication of user confirmation ofthe confirmation request is received from the third external electronicdevice (e.g., block 931).

At block 1338, in some examples, in accordance with receiving theindication of user confirmation of the confirmation request, theresponse to the natural language speech input is provided (e.g., block950).

At block 1340, in some examples, it is determined whether the firstlikelihood is less than a third threshold (e.g., a lower threshold)(e.g., block 932).

At block 1342, in some examples, in accordance with determining that thefirst likelihood is less than the third threshold, providing theresponse is forgone. In some examples, in accordance with determiningthat the first likelihood is less than the third threshold, a responseindicative of user non-recognition is provided, as shown in block 1344(e.g., block 951). In some examples, providing the response to thenatural language speech input is performed further in accordance with adetermination that the first likelihood is not less than the thirdthreshold.

At block 1346, in some examples, a second natural language speech inputis received.

At block 1348, in some examples, it is determined whether the secondnatural language speech input corresponds to the first user or thesecond user.

At block 1350, in some examples, in accordance with a determination thatthe second natural language speech input corresponds to the first user,the first speaker profile is updated based on the second naturallanguage speech input. At block 1352, in some examples, in accordancewith a determination that the second natural language speech inputcorresponds to the second user, the second speaker profile is updatedbased on the second natural language speech input.

At block 1354, in some examples, it is determined whether the naturallanguage speech input includes a reference to a person (e.g., block906).

At block 1356, in some examples, in accordance with determining that thenatural language speech input includes the reference to the person: itis determined whether the reference to the person matches a fifth nameof the first user (e.g., block 913).

At block 1358, in some examples, in accordance with determining that thereference to the person matches the fifth name of the first user, athird response to the natural language speech input is provided, thethird response being personalized for the first user (e.g., block 952).In some examples, providing the response to the natural language speechinput is performed in accordance with determining that the naturallanguage speech input does not include the reference to the person.

At block 1360, a digital assistant identifier associated with the firstuser is obtained. In some examples, obtaining the digital assistantidentifier includes providing the first likelihood to an externalelectronic device, as shown in block 1362. In some examples, obtainingthe digital assistant identifier includes receiving the digitalassistant identifier from the external electronic device, where thedigital assistant identifier is determined by the external electronicdevice based on the first likelihood, as shown in block 1364.

At block 1366, in some examples, a communication identifiercorresponding to the obtained digital assistant identifier isdetermined. The communication identifier identifies a fourth externalelectronic device of the plurality of external electronic devices, thefourth external electronic device being associated with the first user.

At block 1368, in some examples, a communication session with the fourthexternal electronic device is established using the communicationidentifier.

At block 1370, in some examples, in accordance with establishing thecommunication session, data associated with the response to the naturallanguage speech input is obtained from the fourth external electronicdevice. In some examples, providing the response to the natural languagespeech input is performed in accordance with obtaining the dataassociated with the response to the natural language speech input.

At block 1372, in some examples, it is determined based on the naturallanguage speech input, whether to identify a user (e.g., block 905). Insome examples, determining the first likelihood and the secondlikelihood are performed in accordance with determining to identify theuser.

In some examples, determining whether to identify a user includesdetermining a user intent associated with the natural language speechinput, as shown in block 1374. In some examples, determining whether toidentify a user includes determining to identify a user in accordancewith determining that the intent includes a personal intent or asemi-personal intent, as shown in block 1376. In some examples,determining whether to identify a user includes determining not toidentify a user in accordance with determining that the intent includesa non-personal intent, as shown in block 1378.

At block 1380, in some examples, in accordance with determining not toidentify the user, providing the response to the natural language speechinput is forgone.

At block 1382, in some examples, in accordance with determining not toidentify the user, a second response to the natural language speechinput is provided (e.g., block 953). In some examples, providing theresponse to the natural language speech input is performed in accordancewith determining to identify the user.

The operations described above with reference to FIGS. 13A-G areoptionally implemented by components depicted in FIGS. 1-4, 6A-B, 7A-C,8, 10A-H, and 12. For example, the operations of process 1300 may beimplemented by device 800, device 900, system 1200, or any combinationor sub-combination thereof. It would be clear to a person havingordinary skill in the art how other processes are implemented based onthe components depicted in FIGS. 1-4, 6A-B, 7A-C, 8, 10A-H, and 12.

8. Process for Providing Media Content

FIGS. 14A-E illustrate process 1400 for providing media content,according to various examples. Process 1400 is performed, for example,using one or more electronic devices implementing a digital assistant.In some examples, process 1400 is performed using a client-server system(e.g., system 100), and the blocks of process 1400 are divided up in anymanner between the server (e.g., DA server 106) and a client device. Inother examples, the blocks of process 1400 are divided up between theserver and multiple client devices (e.g., a mobile phone and a smartwatch). Thus, while portions of process 1400 are described herein asbeing performed by particular devices of a client-server system, it willbe appreciated that process 1300 is not so limited. In other examples,process 1400 is performed using only a client device (e.g., user device104) or only multiple client devices. In process 1400, some blocks are,optionally, combined, the order of some blocks is, optionally, changed,and some blocks are, optionally, omitted. In some examples, additionalsteps may be performed in combination with process 1400.

At block 1402, a spoken media request is received (e.g., block 1102).

At block 1404, it is determined whether a user, of a plurality ofregistered users, corresponds to the spoken media request (e.g., block1106).

At block 1406, in accordance with determining that a first user of theplurality of registered users corresponds to the spoken media request, afirst response to the spoken media request is provided, the firstresponse being personalized for the first user (e.g., block 1108). Insome examples, the spoken media request includes a name of a second userof the plurality of registered users. In some examples, the second userof the plurality of registered users is different from the first user ofthe plurality of registered users. In some examples, the first responseto the spoken media request includes playback of media item associatedwith the second user. In some examples, the spoken media requestincludes a name of a media collection associated with a third user ofthe plurality of registered users. In some examples, the third user ofthe plurality of registered users is different from the first user ofthe plurality of registered users. In some examples, the first responseto the spoken media request includes playback of a media item from themedia collection associated with the third user.

In some examples, the first response to the spoken media requestincludes one or more words indicative of personalization for the firstuser. In some examples, the one or more words include a name of thefirst user. In some examples, the first response to the spoken mediarequest includes playback of a media item from a first media accountassociated with the first user. In some examples, providing the firstresponse to the spoken media request includes updating a second mediaaccount associated with the first user.

At block 1408, in some examples, in accordance with determining that thefirst user of the plurality of registered users corresponds to thespoken media request: a media preference of the first user is updatedbased on the spoken user request. In some examples, the spoken mediarequest includes a request to switch a content provider. In someexamples, the first response to the spoken media request indicates thatthe content provider has been switched. In some examples, updating themedia preference of the first user includes updating a content providerpreference of the first user based on the spoken media request, as shownin block 1410.

At block 1412, in some examples, in accordance with determining that nouser of the plurality of registered users corresponds to the spokenmedia request, updating any media preference of any user based on thespoken media request is forgone.

At block 1414, in accordance with determining that no user of theplurality of registered users corresponds to the spoken media request:it is determined whether the spoken media request includes a personalmedia request (e.g., block 1110).

In some examples, determining whether the spoken media request includesa personal media request includes: determining that the spoken mediarequest includes one or more words indicative of personalization, asshown in block 1416. In some examples, determining whether the spokenmedia request includes a personal media request includes: determiningthat the spoken media request is associated with a predetermined type ofuser intent, as shown in block 1418.

At block 1420, in accordance with determining that the spoken mediarequest includes a personal media request: an identification of a userwho provided the spoken media request is obtained (e.g., block 1112). Insome examples, obtaining the identification of the user who provided thespoken media request includes: providing an output indicative of arequest for user identity (block 1422), in response to providing theoutput indicative of the request for user identity, receiving a speechinput (block 1424), and obtaining the identification based on the speechinput (block 1426).

At block 1428, in accordance with obtaining the identification: secondresponse to the spoken media request is provided, the second responsebeing personalized for the user who provided the spoken media request(e.g., block 1108).

At block 1430, in some examples, in accordance with determining that nouser of the plurality of registered users corresponds to the spokenmedia request and in accordance with determining that the spoken mediarequest does not include a personal media request, it is determinedwhether a media account of a first type is associated with theelectronic device (e.g., block 1116).

At block 1432, in some examples, in accordance with determining that amedia account of the first type is associated with the electronicdevice: a third response to the spoken media request is provided, thethird response being based on the media account of the first type (e.g.,block 1118).

At block 1434, in some examples, in accordance with determining that amedia account of the first type is not associated with the electronicdevice: a fourth response to the spoken media request is provided, thefourth response being based on a media account of a second typedifferent from the first type (e.g., block 1120).

At block 1436, in some examples, it is determined that a plurality ofusers of the plurality of registered users correspond to the spokenmedia request (e.g., block 1106).

At block 1438, in some examples, in accordance with determining that theplurality of users correspond to the spoken media request: it isdetermined whether the spoken media request includes a personal request(e.g., block 1122).

At block 1440, in some examples, in accordance with determining that thespoken media request includes a personal request: it is determinedwhether a media account of a third type is associated with theelectronic device (e.g., block 1124).

At block 1442, in some examples, in accordance with determining that amedia account of the third type is associated with the electronicdevice, it is determined whether a user associated with the mediaaccount of the third type is a user of the plurality of users (e.g.,block 1126).

At block 1444, in some examples, in accordance with determining that theuser associated with the media account of the third type is a user ofthe plurality of users, a fifth response to the spoken media request isprovided, the fifth response being based on the media account of thethird type (e.g., block 1128).

At block 1446, in some examples, in accordance with determining that thespoken media request does not include a personal request: a sixthresponse to the spoken media request is provided, the sixth responsebeing based on a media account associated with the electronic device(e.g., blocks 1118 or 1120).

The operations described above with reference to FIGS. 14A-E areoptionally implemented by components depicted in FIGS. 1-4, 6A-B, 7A-C,8, 10A-H, and 12. For example, the operations of process 1400 may beimplemented by device 800, device 900, system 1200, or any combinationor sub-combination thereof. It would be clear to a person havingordinary skill in the art how other processes are implemented based onthe components depicted in FIGS. 1-4, 6A-B, 7A-C, 8, 10A-H, and 12.

In accordance with some implementations, a computer-readable storagemedium (e.g., a non-transitory computer readable storage medium) isprovided, the computer-readable storage medium storing one or moreprograms for execution by one or more processors of an electronicdevice, the one or more programs including instructions for performingany of the methods or processes described herein.

In accordance with some implementations, an electronic device (e.g., aportable electronic device) is provided that comprises means forperforming any of the methods or processes described herein.

In accordance with some implementations, an electronic device (e.g., aportable electronic device) is provided that comprises a processing unitconfigured to perform any of the methods or processes described herein.

In accordance with some implementations, an electronic device (e.g., aportable electronic device) is provided that comprises one or moreprocessors and memory storing one or more programs for execution by theone or more processors, the one or more programs including instructionsfor performing any of the methods or processes described herein.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to identify auser to provide personalized responses. The present disclosurecontemplates that in some instances, this gathered data may includepersonal information data that uniquely identifies or can be used tocontact or locate a specific person. Such personal information data caninclude demographic data, location-based data, telephone numbers, emailaddresses, twitter IDs, home addresses, data or records relating to auser's health or level of fitness (e.g., vital signs measurements,medication information, exercise information), date of birth, or anyother identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toidentify a user and provide information relevant to the identified user.Accordingly, use of such personal information data enables devices toprovide personalized responses. Further, other uses for personalinformation data that benefit the user are also contemplated by thepresent disclosure. For instance, health and fitness data may be used toprovide insights into a user's general wellness, or may be used aspositive feedback to individuals using technology to pursue wellnessgoals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof collecting speaker profiles for users, the present technology can beconfigured to allow users to select to “opt in” or “opt out” ofparticipation in the collection of personal information data duringregistration for services or anytime thereafter. In another example,users can select not to provide speaker profiles (and/or other personalinformation). In yet another example, users can select to limit thelength of time speaker profiles are maintained or entirely prohibit thedevelopment of a speaker profile. In addition to providing “opt in” and“opt out” options, the present disclosure contemplates providingnotifications relating to the access or use of personal information. Forinstance, a user may be notified upon downloading an app that theirpersonal information data will be accessed and then reminded again justbefore personal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data at a city level rather than at an addresslevel), controlling how data is stored (e.g., aggregating data acrossusers), and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, responses canbe provided to user speech inputs based on non-personal information dataor a bare minimum amount of personal information, such as the contentbeing requested by the device associated with a user, other non-personalinformation available to the device, or publicly available information.

What is claimed is:
 1. A non-transitory computer-readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by one or more processors of anelectronic device, cause the electronic device to receive a spoken mediarequest; determine whether a user, of a plurality of registered users,corresponds to the spoken media request; in accordance with determiningthat a first user of the plurality of registered users corresponds tothe spoken media request: provide a first response to the spoken mediarequest, the first response being personalized for the first user; andin accordance with determining that no user of the plurality ofregistered users corresponds to the spoken media request: determinewhether the spoken media request includes a personal media request; inaccordance with determining that the spoken media request includes apersonal media request: obtain an identification of a user who providedthe spoken media request; and in accordance with obtaining theidentification: provide a second response to the spoken media request,the second response being personalized for the user who provided thespoken media request.
 2. The non-transitory computer-readable storagemedium of claim 1, wherein the one or more programs further includeinstructions, which when executed by the one or more processors, causethe electronic device to: in accordance with determining that no user ofthe plurality of registered users corresponds to the spoken mediarequest and in accordance with determining that the spoken media requestdoes not include a personal media request: determine whether a mediaaccount of a first type is associated with the electronic device; inaccordance with determining that a media account of the first type isassociated with the electronic device: provide a third response to thespoken media request, the third response being based on the mediaaccount of the first type; and in accordance with determining that amedia account of the first type is not associated with the electronicdevice: provide a fourth response to the spoken media request, thefourth response being based on a media account of a second typedifferent from the first type.
 3. The non-transitory computer-readablestorage medium of claim 1, wherein the one or more programs furtherinclude instructions, which when executed by the one or more processors,cause the electronic device to: determine that a plurality of users ofthe plurality of registered users correspond to the spoken mediarequest; in accordance with determining that the plurality of userscorrespond to the spoken media request: determine whether the spokenmedia request includes a personal request.
 4. The non-transitorycomputer-readable storage medium of claim 3, wherein the one or moreprograms further include instructions, which when executed by the one ormore processors, cause the electronic device to: in accordance withdetermining that the spoken media request includes a personal request:determine whether a media account of a third type is associated with theelectronic device; and in accordance with determining that a mediaaccount of the third type is associated with the electronic device:determine whether a user associated with the media account of the thirdtype is a user of the plurality of users; and in accordance withdetermining that the user associated with the media account of the thirdtype is a user of the plurality of users, provide a fifth response tothe spoken media request, the fifth response being based on the mediaaccount of the third type.
 5. The non-transitory computer-readablestorage medium of claim 3, wherein the one or more programs furtherinclude instructions, which when executed by the one or more processors,cause the electronic device to: in accordance with determining that thespoken media request does not include a personal request: provide asixth response to the spoken media request, the sixth response beingbased on a media account associated with the electronic device.
 6. Thenon-transitory computer-readable storage medium of claim 1, whereindetermining whether the spoken media request includes a personal mediarequest includes: determining that the spoken media request includes oneor more words indicative of personalization.
 7. The non-transitorycomputer-readable storage medium of claim 1, wherein determining whetherthe spoken media request includes a personal media request includes:determining that the spoken media request is associated with apredetermined type of user intent.
 8. The non-transitorycomputer-readable storage medium of claim 1, wherein obtaining theidentification of the user who provided the spoken media requestincludes: providing an output indicative of a request for user identity;in response to providing the output indicative of the request for useridentity, receiving a speech input; and obtaining the identificationbased on the speech input.
 9. The non-transitory computer-readablestorage medium of claim 1, wherein: the spoken media request includes aname of a second user of the plurality of registered users; the seconduser of the plurality of registered users is different from the firstuser of the plurality of registered users; and the first response to thespoken media request includes playback of a media item associated withthe second user.
 10. The non-transitory computer-readable storage mediumof claim 1, wherein: the spoken media request includes a name of a mediacollection associated with a third user of the plurality of registeredusers; the third user of the plurality of registered users is differentfrom the first user of the plurality of registered users; and the firstresponse to the spoken media request includes playback of a media itemfrom the media collection associated with the third user.
 11. Thenon-transitory computer-readable storage medium of claim 1, wherein theone or more programs further include instructions, which when executedby the one or more processors, cause the electronic device to: inaccordance with determining that the first user of the plurality ofregistered users corresponds to the spoken media request: update a mediapreference of the first user based on the spoken media request; and inaccordance with determining that no user of the plurality of registeredusers corresponds to the spoken media request: forgo updating any mediapreference of any user based on the spoken media request.
 12. Thenon-transitory computer-readable storage medium of claim 11, wherein:the spoken media request includes a request to switch a contentprovider; the first response to the spoken media request indicates thatthe content provider has been switched; and updating the mediapreference of the first user includes updating a content providerpreference of the first user based on the spoken media request.
 13. Thenon-transitory computer-readable storage medium of claim 1, wherein thefirst response to the spoken media request includes one or more wordsindicative of personalization for the first user.
 14. The non-transitorycomputer-readable storage medium of claim 13, wherein the one or morewords include a name of the first user.
 15. The non-transitorycomputer-readable storage medium of claim 1, wherein the first responseto the spoken media request includes playback of a media item from afirst media account associated with the first user.
 16. Thenon-transitory computer-readable storage medium of claim 1, whereinproviding the first response to the spoken media request includesupdating a second media account associated with the first user.
 17. Anelectronic device, comprising: one or more processors; a memory; and oneor more programs, wherein the one or more programs are stored in thememory and configured to be executed by the one or more processors, theone or more programs including instructions for: receiving a spokenmedia request; determining whether a user, of a plurality of registeredusers, corresponds to the spoken media request; in accordance withdetermining that a first user of the plurality of registered userscorresponds to the spoken media request: providing a first response tothe spoken media request, the first response being personalized for thefirst user; and in accordance with determining that no user of theplurality of registered users corresponds to the spoken media request:determining whether the spoken media request includes a personal mediarequest; in accordance with determining that the spoken media requestincludes a personal media request: obtaining an identification of a userwho provided the spoken media request; and in accordance with obtainingthe identification: providing a second response to the spoken mediarequest, the second response being personalized for the user whoprovided the spoken media request.
 18. A method for providing mediacontent, the method comprising: at an electronic device with one or moreprocessors and memory: receiving a spoken media request; determiningwhether a user, of a plurality of registered users, corresponds to thespoken media request; in accordance with determining that a first userof the plurality of registered users corresponds to the spoken mediarequest: providing a first response to the spoken media request, thefirst response being personalized for the first user; and in accordancewith determining that no user of the plurality of registered userscorresponds to the spoken media request: determining whether the spokenmedia request includes a personal media request; in accordance withdetermining that the spoken media request includes a personal mediarequest: obtaining an identification of a user who provided the spokenmedia request; and in accordance with obtaining the identification:providing a second response to the spoken media request, the secondresponse being personalized for the user who provided the spoken mediarequest.